I’ve been experimenting running with the transactions shut off. Even with transactions shut off it seems like the db file never gets written to unless I call commit on the RecordManager. Is this the expected behavior?
Your description gave me the impression that the cached updates would be periodically written to the database file by jdbm and that there was no reason to call commit on the RecordManager directly.
On Behalf Of Kevin Day
Sent: Monday, January 16, 2006 4:23 PM
To: JDBM General listserv
Subject: re: [Jdbm-general] Transaction memory size
No - when transactions are disabled, they are cached and commited to disk periodically (behind the scenes, we manage the size of the uncomitted page load and write to disk as necessary). When Tx are off, writes go to only one file (the db file), instead of writing to the log, then to the db file.
Because writes to the log are actually synced to the phyiscal disk they are usually considerably slower than non-transactional writes.
Running without transactions should be several times faster than running with them (at the risk of corrupting the database file in the event of a crash, of course).
------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ Jdbm-general mailing list Jdbmfirstname.lastname@example.org https://lists.sourceforge.net/lists/listinfo/jdbm-general