🚀 go-pugleaf

In article <1gli95INNid5@cat.cis.Brown.EDU> JIM@brownvm.brown.edu (James Mathiesen) writes:

>A more elegent solution is to let dbz() have a write-through cache,
>this lets .pag be kept in memory, but updates are written to disk
>as they occur.  I'm enclosing patches below to dbz.c, dbz.h and
>his.c that add and use dbzwritethough().

Excuse my ignorance, but would it be better if the history.pag file was
mmap()'ed?  that way, a simple fsync() call would write out just the
changes rather than the entire file.

Also, having a dbzsync() every 10 articles is pretty insane.  I've
changed mine to 50, though I'd think 500 would be respectable.

Just curious,

Tom
-- 
Tom Limoncelli -- tal@warren.mentorg.com (work) -- tal@plts.uucp (play)
Reality is stranger than fiction #943247:  The IRS granted
ANS approval as a 501c3 "charity" on September 14, 1992.