Jorgen Lundman wrote:
> Now repeat the db_stat call and see how long it takes the 2nd
It does indeed speed up, if I do not wait too long between tests.
If it slows down after you wait a while, that means some other process on the
machine is using the system RAM and forcing the BDB data out of the system
cache. Find out what other program is hogging the memory, it's obvious that
BDB is not doing anything wrong on its own.
4 seconds is much nicer. So what you are saying is that BDB uses mmap, and
operations inside this memory will trigger reads inside the kernel which do not
show as libc syscalls. Rats. So it may be IO? I need to throw even more memory
at it, and live with the increasing startup times?
How does the "set_cachesize" relate to the mmap usage?
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/