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

RE: Issues in Performance Tesing of OpenLDAP using SLAMD

Both the benchmarking servers have Solaris 10 - x86.
I am not sure about the Memory Management S/w. Is it the one bundled with OpenLDAP or is it the one , the server uses.

My understanding is that, it may help but currently, we are not facing any memory related issues in running the tests.

The values for set_cachesize was set to 1  0  1 as that is the value we have in the production system.
Though it should be 2 0 1 as suggested in DB_CONFIG documentation.
Can this be a cause of the problems that we are facing.

The following is the list of problems that we have been facing in our Benchmarking activity -

Shilpa Sethi

Plot 6, Electronic City,
Sector - 18,
Gurgaon 122015
Haryana, India

-----Original Message-----
From: Quanah Gibson-Mount [mailto:quanah@zimbra.com]
Sent: Friday, November 21, 2008 12:03 AM
To: Shilpa Sethi; Howard Chu
Cc: openldap-technical@openldap.org
Subject: RE: Issues in Performance Tesing of OpenLDAP using SLAMD

--On Thursday, November 20, 2008 7:59 PM +0530 Shilpa Sethi
<shilpa2.sethi@aricent.com> wrote:

> Hi,
> Information that you asked for was provided in the first mail to the
> forum about the issue. http://markmail.org/message/bqkx6tk5gmc3fuw4

What OS?  What memory manager? Have you verified that DB_CONFIG is properly
tuned (i.e., how did you come up with the 1 0 1 setting?) etc.



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."