Performance Comparison of OpenLDAP running on Midrange- and Highend machine

This page describes a performance test of the OpenLDAP server on a highend machine (Intel Quadcore, 2GB RAM) and a midrange machine (Intel Dualcore, 1GB RAM). The client request policy is based on the cognitions described here (TOBEDONE ). The testscript is described and can be found here (TOBEDONE).

In the following 'sec' is a abbreviation for seconds.

Response time graphs

The graphs below show three test runs. Each is represented by another color (red, green , blue). The point in the graphs represent the measured response time for one ldapsearch process.

Midrange machine test (Graph 1)

The OS is SLC3 and the OpenLDAP version is 2.0.27-22

Midrange machine test SLC4 (Graph 1.1)

The OS is SLC4 and the OpenLDAP version is 2.2.13-7.4E

Highend machine test (Graph 2)

The OS is SLC4.5 and the OpenLDAP version is 2.2.13-7.4E

more Graphs can be found in SlapdQuadcoreTest

Result

Looking at the graphs shown above, one can see that OpenLDAP handles most of the request nicely. However, the green and blue point clowds in Graph1 show that a certain amount of requests take longer. In fact, much longer!

Out of 1674 in total, 1614 are handles between 0.04 and 0.9 sec (average 0.19) , 54 between 3 and 3.4 sec (average 3.19) and 6 between 9 and 9.3 sec (average 9.17).

# of requests	response time [sec]
1614	0.04 -0.19
54	3 - 3.4
6	9 - 9.17

This leads to the assumption that the OpenLDAP server component can only handle a certain amount of requests at a time. It is interesting, if the connections are accepted by the server but not served, or if the clients have to wait until a request handled thread is available for a new connection. This has not been investigated in this test.

Below, you'll find a table which shows how many requests took how much time in average for being finished.

percentage	avg. time [sec]
96,41%	0.19
3,22%	3.19
0.36%	9.17

-- FelixNikolausEhm - 04 Jul 2007