On Thursday 05 October 2006 20:58, Rob Tanner wrote: > Hi, > > I'm replacing an old Netscape server running on a 296 MHz dual processor > Solaris 5.7 (sun4u sparc) box with OpenLDAP 2.3.27 running on a single > 2.4GHz processor Intel box running Fedora Core 4. I have duplicated one > of my hierarchies -- approx 9000 entries. There is an index on an > attribute called deptaffiliationcodes (on both systems) which I'm using > as a search filter to make sure everything is working. Dumping the > results to /dev/null, a search on the Netscape server takes typically 35 > milliseconds to complete. The exact same search on the OpenLDAP server > takes between 2.5 to 3.5 seconds. And that's way too slow for me to put > the OpenLDAP server into production. > > I am using the bdb backend and the example DB_CONFIG file which sets the > cache size to 268435456 bytes, which is bigger than the actual size of > dn2id.bdb and id2entry.bdb combined (about 16Mb). What other factors > can affect performance? Just some anecdotal encouragement, my workstation (Mandriva 2007 x86_64 with 2.3.27) has a copy of our whole tree, ~ 1.5 million entries (in 3 databases, a bit more than the size of id2entry+dn2id configured as cache for each db), and it does a local exact search on an indexed attribute in under 10ms. Doing the same search to our production servers running RHEL4 with .3.27 (over the network) does about the same ... You may want to post more details on your configuration (index settings, idlcache etc.) and how you are testing (what search etc.). Regards, Buchan -- Buchan Milne ISP Systems Specialist - Monitoring/Authentication Team Leader B.Eng,RHCE(803004789010797),LPIC-2(LPI000074592)
Attachment:
pgpyb2X3crvVP.pgp
Description: PGP signature