Hi,
Thanks a lot for the quick reply.
I Tried out further tests with a set of 50 clients with 1 thread. I used 2 slamd client manager from 2 different DL585 machines, Further, Started 50 clients on both the servers making in all 100 SLAMD clients.
The results obtained with the tests with 60, 80 and 100 clients resulted in CPU Utilization of 100% in the initial run of ten minutes. CPU reported an average of 100% utilized while after 10 minutes, it started oscillating between 0% utilized and 100% utilized, resulting in slow down of average.
Can you please suggest any other tool/ way to achieved a sustained CPU utilization of about 70% by generating read load on openLDAP.
Currently the CPU graph shows spikes with shoot up in utilization and then a sudden drop. It would be great, if you could suggest some possible reasons for this behavior.
Also what is the average response time of a read request in a heavy load scenario for openLDAP ?
Thanks a ton in advance.
Regards Shilpa Sethi
A R I C E N T Plot 6, Electronic City, Sector - 18, Gurgaon 122015 Haryana, India
-----Original Message----- From: Quanah Gibson-Mount [mailto:quanah@zimbra.com] Sent: Monday, November 10, 2008 9:51 PM To: Shilpa Sethi; openldap-technical@openldap.org Subject: Re: Issues in Performance Tesing of OpenLDAP using SLAMD
--On Monday, November 10, 2008 5:28 PM +0530 Shilpa Sethi shilpa2.sethi@aricent.com wrote:
Please suggest a way by which Predictable/ similar read rates could be achieved on both the servers as both being exactly same.
I always found slamd to be massively inefficient. The only way to get reliable results from it in a read scenario was to have numerous client systems querying the LDAP server(s), so that the clients could reliably max out the server.
--Quanah
--
Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration
"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."