On 5/22/08 12:59 PM, Quanah Gibson-Mount wrote:
set_cachesize 0 524288000 2 set_lg_bsize 2097152 set_lg_regionmax 262144
Have I missed something that would be more reasonable?
I don't know without knowing the size of your accesslog db. ;)
Sorry...
My accesslog DB currently has just over 48000 entries. The automatic purging runs every 8 hours and gets rid of everything that is older than 5 days.
If you wanted the actual file sizes: -rw-r--r-- 1 ldap ldap 383 Jan 30 2006 DB_CONFIG -rw------- 1 ldap ldap 24576 Jul 10 2007 __db.006 -rw------- 1 ldap ldap 450560 Jul 10 2007 __db.005 -rw------- 1 ldap ldap 2359296 Jul 10 2007 __db.004 -rw------- 1 ldap ldap 262144000 Jul 10 2007 __db.003 -rw------- 1 ldap ldap 262144000 Jul 10 2007 __db.002 -rw------- 1 ldap ldap 16384 Jul 10 2007 __db.001 -rw------- 1 ldap ldap 1323008 May 22 13:05 reqStart.bdb -rw------- 1 ldap ldap 679936 May 22 13:05 reqResult.bdb -rw------- 1 ldap ldap 1323008 May 22 13:05 reqEnd.bdb -rw------- 1 ldap ldap 2732032 May 22 13:05 objectClass.bdb -rw------- 1 ldap ldap 79740928 May 22 13:05 id2entry.bdb -rw------- 1 ldap ldap 1327104 May 22 13:05 entryCSN.bdb -rw------- 1 ldap ldap 12718080 May 22 13:05 dn2id.bdb -rw-r--r-- 1 ldap ldap 4096 May 22 13:05 alock
Personally I avoid splitting memory regions if possible, but that may only apply to BDB 4.2.52, I've never tested that aspect of configuration with anything more recent.
I am running 4.2.52... and the split memory regions are a carry over from when this was running on a 2GB machine and it seemed to run better with multiple segments (or at least that was the theory at the time).