http://www.sleepycat.com/update/4.2.XX/if.4.2.XX.html
--On Thursday, November 20, 2003 12:38 PM -0900 Matthew Schumacher <matt.s@aptalaska.net> wrote:
From the reading I have been doing on this list, this is a bdb bug that has no known timeline for a fix. Some people say it's avoidable by setting a large cache size (big enough for your entire db) in your DB_CONFIG file. Others avoid the problem by using solaris.
List: Please correct me if I'm wrong, but that is the conclusion I have come to dealing with this problem.
Anyone know exactly what is going wrong in bdb, are they aware of the bug?
I use solaris AND put everything into a cache. I believe BDB 4.2 is supposed to have fixes to the problem, but not having a proper cache size will still cause performance issues.
--Quanah
-- Quanah Gibson-Mount Principal Software Developer ITSS/TSS/Computing Systems ITSS/TSS/Infrastructure Operations Stanford University GnuPG Public Key: http://www.stanford.edu/~quanah/pgp.html