[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Progressive service degradation
Hello,
I've been running some saturation tests against OpenLDAP
and have not yet been satisfied that I have things
configured correctly. The level of service is
acceptable for the first two hours, but during the third
hour, performance drops. It continues to plummet over
the course of the next 9 hours (it was an 12-hour
test). Here are the specific technical details:
Server
Red Hat 7.1
OpenLDAP 2.0.11 - compiled from source
Berkeley db 3.1.17 - from Red Hat RPM
Pentium III 733
256mb RAM
10mb Ethernet
Client
NT 4.0
DirectoryMark 1.2
Pentium II 450
128mb RAM
10mb Ethernet
Here's the performance stats:
Hour Avg Time Transactions Fails Timeouts ops/sec
(ms)
0100 289 123,961 37 4 34.4
0200 309 115,924 34 3 32.2
0300 486 73,837 18 2 20.5
0400 749 47,987 13 1 13.3
0500 957 37,595 20 13 10.4
0600 1,158 31,067 52 41 8.6
0700 1,325 27,173 106 93 7.5
0800 1,490 24,169 115 106 6.7
0900 1,613 22,315 149 137 6.2
1000 1,745 20,642 181 168 5.7
1100 1,865 19,305 217 181 5.4
1200 1,974 18,233 237 211 5.1
Here are the relevant configuration settings from
slapd.conf:
LDAP_Version_3
loglevel 0
idletimeout 30
sizelimit 500
timeout 3600
defaultsearchbase "dc=company,dc=com"
index objectClass eq,pres
index cn eq,sub
index sn eq
index description eq
index seeAlso eq
dbnolocking
dbnosync
cachesize 1500
dbcachesize 15000000
DirectoryMark is configured to use the search base
of "dc=company,dc=com". All searches are using an
anonymous bind. There is no delay between searches.
Each DirectoryMark test executes for 60 minutes, and
then writes out it's results.
I would like to know what additional configuration can
be performed in order to maintain an acceptable level of
performance over a longer period of time than two hours.
Thanks in advance,
Kayne McGladrey
k.mcgladrey@worldnet.att.net