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

Issues in Performance Tesing of OpenLDAP using SLAMD

Hi all,

 

Currently I am involved in an activity that deals with measuring performance of OpenLDAP on Solaris 10 – x_86 machine.

 

Hardware Specs –

  1. Two identical servers (Servers ‘NodeA’ and ‘NodeB’) with the following configuration:
    1. Sun Fire X4200 M2 x64 Server
    2. 2x AMD Opteron Model 2220 (2.8GHz/1MB) processor
    3. 1x 4GB PC2-5300 DDR2-667 memory
    4. 2x 146GB HDD 15K RPM (Hardware RAID-1, so available disk space is 146 GB).
  2. One server ‘NodeC’ is used as a traffic injector and has the following hardware configuration:
    1. Sun Fire X4200 M2 x64 Server
    2. 2x AMD Opteron Model 2218
    3. 4x 2GB PC2-5300 DDR2-667 memory
    4. 4x 73GB HDD 10K RPM.

Software installation common to all servers:

  1. JDK 1.6
  2. Symas CDS Version 3.9.3

 

For traffic injection, SLAMD v2.0.0-alpha1 is installed on NodeC.

 

Both Node A and B are Mirror-Mode replicas.

 

The database is having 1 Million subscribers and both the cache sizes are set as follows in slapd.conf :

cachesize       250000

idlcachesize    250000 i.e 25% of the subscriber base.

 

Two identical SLAMD SearchRate Jobs, one pointing to Node A and other to Node B are run from Node C.

However, there is a wide difference in the number of lookups/sec performed in both the servers.

 

The read rates obtained vary in the ratio of 1:7 or so on both the servers.

 

I am using 1 SLAMD client and 2 threads for targeting on 1 server.

 

If I increase the number of thread, SLAMD starts reporting exceptions.

 

Please suggest a way by which Predictable/ similar read rates could be achieved on both the servers as both being exactly same.

 

Thanks a ton in advance for suggesting a solution.

 

Regards

Shilpa Sethi

 

A R I C E N T

Plot 6, Electronic City,

Sector - 18,

Gurgaon 122015

Haryana, India 

 

 


"DISCLAIMER: This message is proprietary to Aricent and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error,please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. Aricent accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus."