[916] in Coldmud discussion meeting

root meeting help first first in chain previous in chain previous next last

Re: [COLD] More efficient diskbasing

daemon@ATHENA.MIT.EDU (Wed Feb 7 20:19:12 1996 )

Date: Wed, 7 Feb 1996 17:54:45 -0700 (MST)
From: "Terrence M. Drozdowski" <xymox@mcmuse.mc.maricopa.edu>
To: coldstuff@cold.org
In-Reply-To: <199602072049.VAA29595@regoc.srce.hr>
Reply-To: coldstuff@cold.org

On Wed, 7 Feb 1996, Miroslav Silovic wrote:

> It just occured to me that most of the checkpointing time is wasted on
> cp - the database has to be copied clean. I thought of a way to keep the
> database clean 95% of the time. This would also make the server a lot safer.
> The thing that would have to be modified is the cache handling. I suggest
> that modified objects could be kept in RAM till the next checkpoint, and
> the checkpoint would be when a) 30 minutes (or whatever) passes, or b)
> more than 75% of the cached objects are modified. Then we could dump
> just the modified objects, and the database would be non-clean only during
> the dump, the cp being unnecessary.
> What do you all think about this?
> 	Jenner

This sounds good, but how much RAM would this eat up?  Would it inflate 
dramaticly or unnoticably?  On a busy coldmud, I'd assume that if you 
have a lot of object creation, you'd have more frequent checkpointing.  
Though, that's just how it seems to me...

Terrence Drozdowski|"Statism is statism by any name the same, apathy is suicide
xymox@mcmuse.mc.maricopa.edu|and we will bare the blame." -1994 PsykoSonik