On Mon, 2005-09-19 at 12:02 -0700, Bill Whillers wrote: > From what I've learned (mostly from the generous people on this list), our > local mysql, Storable and other usages does a great job at meeting those > needs. In reality, the ideal case would be if our data were non-changing and > could simply be loaded at server start up. So, anything that emulates that > non-lossy effect across multiple machines and changing data, comparable > efficiency, and perhaps elimination of the freeze/thaw step altogether would > be great.
If it has to work across multiple machines, you will need to use a daemon like MySQL. If it's local to one machine, BerkeleyDB or Cache::FastMmap can beat it. Compression (using zlib) tends to speed things up a bit when pushing huge amounts of data into MySQL across a socket connection, so you might want to add that in as well. - Perrin
