in reply to GDBM_File to memory?

Hmm, this sounds very odd to me. Any OS worth its salt should be caching the hot data in RAM so that the access speed of the disk does not totally bog the process down. So either you have too little RAM for this task or your OS isn't doing it's job properly. Or you've got the filesystem mounted in sync mode which forces it to constantly write changes back to the disk

Which OS is this (and if it's a *NIX, what filesystem with what mount options are you using)?.


Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it. -- Brian W. Kernighan

Replies are listed 'Best First'.
Re^2: GDBM_File to memory?
by keymon (Beadle) on Dec 23, 2005 at 19:32 UTC
    It's a RAID5 disk. As I mentioned in the update above, not having the GDBM_FAST flag made it go to disk for each and every operation. On a RAID5, this is a killer. I added the flag, and the run time went from days to a couple of minutes :)
[reply]

In Section Seekers of Perl Wisdom