Berkeley DB Family

Hi,

I had an idea. The docs say: "If the cache becomes full of page copies before the old copies can be discarded, additional I/O will occur as pages are written to temporary "freezer" files. This can substantially reduce throughput, and should be avoided if possible by configuring a large cache and keeping snapshot isolation transactions short."

How about allocating a new cache file (of the same size as the original) in the env instead of creating hundreds (or more) freezer files when the cache is overflowing ? One can have multiple cache files already by specifying the cache in multiple segments. What's particularly irksome about these freezer files is that they stick around, even past checkpoints and restarts.

Could this work ?

Andi..