Is there any way to avoid double buffering in the Berkeley DB system?
While you cannot avoid double buffering entirely, there are a few things you can do to address this issue: First, the Berkeley DB cache size can be explicitly set. Rather than allocate additional space in the Berkeley DB cache to cover unexpectedly heavy load or large table sizes, double buffering may suggest you size the cache to function well under normal conditions, and then depend on the file buffer cache to cover abnormal conditions. Obviously, this is a trade-off, as Berkeley DB may not then perform as well as usual under abnormal conditions. Second, depending on the underlying operating system you’re using, you may be able to alter the amount of physical memory devoted to the file buffer cache. Running as the system super-user makes a difference for some UNIX or UNIX-like operating systems as well. Third, changing the size of the Berkeley DB environment regions can change the amount of space the operating system makes available for the file buffer cache, and it’s often worth con
