[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: performance tuning

Yes, ultimately this will be used in a web-based application, and that's why we
are using a cgi script to test. Is this a bad idea? should I be directly testing the
OpenLDAP server?

It is using back_bdb. I have removed the dbcachesize parameter.

Quanah Gibson-Mount wrote:
--On Thursday, July 05, 2007 3:57 PM -0400 Jason Peters <jlpeters@ispalliance.net> wrote:

I am testing an OpenLDAP server with 3000 fake 'people' entries, but it
does not perform as well as I would expect. I have added some tweaks
based on my research of the documentation. Is there anything I am
missing here? Is there any way to further tune this setup?

I have written a script to test the directory. It is written in
PHP using the standard LDAP libraries. Both the script, and the
LDAP server are running on the same box. The script  is
calling the server via the public interface (not the loopback) using
standard port 80. It basically does a search on a matching query.
The search query was "sn=BE*". Below is the info for my setup:


LDAP uses port 389, not 80.  Sounds like you are testing a web server?

Linux Debian etch system

OpenLDAP version:
# /usr/sbin/slapd -V
@(#) $OpenLDAP: slapd 2.3.30 (Mar  9 2007 05:43:02) $


Here are my additions to the slapd.conf file (other than these, the file
is essentially like the default):


###############################################
# Performance tweaks added by me -JLP

index sn subinitial


What database backend are you using? ldbm? dbcachesize is not a parameter for back-bdb/hdb.

cachesize 100000
dbcachesize 1000000


You really don't provide enough information to help.

--Quanah


--
Quanah Gibson-Mount
Principal Software Engineer
Zimbra, Inc
--------------------
Zimbra ::  the leader in open source messaging and collaboration