Balance Checkpoints

[David Merrill]

On Tue, Dec 12, 2000 at 09:22:44PM -0600, Christopher Browne wrote:
> On Tue, 12 Dec 2000 15:22:15 EST, the world broke into rejoicing as
> Consider two cases:

[snipped all over]

> a) Someone who generates an average of ten transactions per month.
>    120 transactions; 12 checkpoints; no performance issue
>    _regardless_ of how we'd implement balance management.
> 
> b) Consider someone generating 1000 transactions per month.
>    Total for the year --> ~ 60 checkpoints across 12000 transactions.
> 
> c) Consider an enterprise with highly skewed activity.
>    Total for the year: 54 checkpoints, which supports 
>    (90 + 3 x 3000) or 9090 transactions.
> 
> The point here is that by keeping the "balance checkpoints"
> a bit dynamic, they can be used strategically to improve 
> performance whilst minimizing their quantity.
> 
> And as for the company for which 365 "checkpoints" in a year isn't
> enough, I'm not sure there's any reasonable option to offer at
> this time...

You make really good sense.

I'd like to be able to tune it to "checkpoint every n days,
or at the end of the day on which you hit t transactions, 
whichever comes first."

-- 
Dr. David C. Merrill                     http://www.lupercalia.net
Linux Documentation Project                dmerrill@lupercalia.net
Collection Editor & Coordinator            http://www.linuxdoc.org
                                       Finger me for my public key

gleemites, n.:
	Petrified deposits of toothpaste found in sinks.
		-- "Sniglets", Rich Hall & Friends