[DGD] DGD and *dbm

[bart at wotf.org]

Seeing how I keep (to me useful) logs around that are many megabytes large,
keeping those in an object would for what I understand impact swapping
performance for that object. Am I mistaken? or is this simply far less of a
concern with DGD/MP?

Trying to think of a workable data model for this makes me come up with a
number of variations, all of which end up in some nested array or an array of
mappings if it has to scale to an imho reasonable size.

What is your suggestion for this?

Bart.

On Mon, 21 Jul 2008 19:16:14 +0200, Felix A. Croes wrote
> Noah Gibbs <noah_gibbs at yahoo.com> wrote:
> 
> > --- On Mon, 7/21/08, Felix A. Croes <felix at dworkin.nl> wrote:
> > > >From DGD/MP's point of view, file reads will be
> > > inefficient and
> > > file writes (or reads with side effects) will be very
> > > inefficient,
> > > progressively more so for a larger number of processors.
> >
> > This seems like it would have significant implications for logging.  Would
logging be significantly deprecated somehow in DGD/MP?  Or would it want to
log to a memory structure of some kind, and just plan to dump it all to file
at thread end?
> 
> Log to an object, view it as a web page served by the mud (or by some
> in-game command).  There's no need to ever log to a file in a
> persistent mud.
> 
> Regards,
> Dworkin
> ___________________________________________
> https://mail.dworkin.nl/mailman/listinfo/dgd

--
Created with Open WebMail at http://www.bartsplace.net/
Read my weblog at http://soapbox.bartsplace.net/