[Date Prev][Date Next]
>Did you look at db_stat before, during, and after this heavy load phase?
Tuning was performed initially to get the best results from the back-end. With the database size increasing over time I have continually monitored lock usage, cache usage, transactions, etc. and made various adjustments to the Berkeley configuration based on documented information from SleepyCat and from two FAQs at OpenLDAP. So hopefully, I have looked at all the available information to me before I have asked for help with this evasive issue. I do not believe that configuration is an issue, but I have taken your suggestion to increase cache size which has not resolved the problem. Other configuration parameters have been modified as well with no relief.
Currently I am pursuing the Berkeley DB upgrade from 4.1.25 to 4.2.52.