Journaling
Fabian Kneubuehl
support at ysd.ch
Tue Apr 17 09:31:26 CDT 2012
Hi,
I run a small benchmark around journaling and .Flush after each
INSERT/UPDATE/DELETE.
I start with a new, empty database and insert a few thousands records. Here
the times
Journaling+Flush: 40 Min.
Journaling only: 3 Min.
Flush only: 4 Min.
None: 3 Min.
This will show you that journaling doesn't cost much time. But as soon as
you make a change an flush this to the DB there will be a huge overhead
(writing to journal, flush to disk, removing flushed data from journal.).
What I still not understand is what journaling exactly does: contains the
.journal file all INSERT/UPDATE/DELETE data since the last flush and after a
crash this data will be inserted into the DB so the user doesn't be aware of
data loss? If this statement is right and I do not flush myself how often
does Valentina call the flush method itself (only if cache is full or all
xxx msec.)?
Regards
Fabian
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macserve.net/pipermail/valentina-beta/attachments/20120417/51446f73/attachment.html>
More information about the Valentina-beta
mailing list