> -----Original Message----- > From: Leone, Todd [mailto:tleone@acs.utah.edu] > Howard, > Thanks for your reply. > Our DB_CONFIG looks like this: > > set_cachesize 3 0 1 > set_lg_regionmax 262144 > set_lg_bsize 2097152 > set_lg_dir /archives/ldap_sec > set_data_dir /ldap_sec_data > > As you can see we've divided home, log and data into three > separate file systems (separate physical drive arrays). > > Running db_stat -m shows no caching problems.. Can you explain > The procedure you touch upon: > > The development code has added an option to store the cache > in shared memory instead. This can be better if your system > can accomodate a large enough shared memory region. > > We would like to give this a try! You need to check out the current HEAD from CVS to try this. Add "shm_key <some integer>" to your bdb database confing in slapd.conf. You will also need to completely rebuild your database, as the database format in the development code is different from the 2.1 release. You will also need to make sure your system allows creating a 3GB shared memory segment, in your case, or break up the cache into multiple smaller segments. -- Howard Chu Chief Architect, Symas Corp. Director, Highland Sun http://www.symas.com http://highlandsun.com/hyc Symas: Premier OpenSource Development and Support
<<attachment: winmail.dat>>