CPU load with request on Uniquemember attribute
Hi All,
I migrate 3 directory server of Iplanet Directory Server 5.1SP4 to Sun One Directory Server 5.2SP4 and since this day, I have several problems on the 3 migrated servers, especially with requests on Uniquemember attribute !!
I already checked the indexes and the attribute Uniquemember is indexed as equality !
Today, requests as this one :
uniqueMember=uid=xxxx responds in 4 seconds instead of 0 seconds in Iplanet Directory Server 5.1SP4.
conn=113624 op=25027 msgId=25028 - RESULT err=0 tag=101 nentries=0 etime=5
It's very strange and I don't know how to find the solution !
Do you have any similar problem ?
Thanks for your help !!
[703 byte] By [
NPTa] at [2007-11-27 5:30:33]
# 1
What other differences exist between your 5.1 servers and your 5.2 servers?
Hardware (CPU, RAM)?
OS?
Tuning (especially cache sizes)?
Plugins?
Has the data remained relatively the same through the upgrade, or are your groups much larger in the 5.2 instance (Large static groups are problematic).
# 2
In 5.1, the servers are in Windows 2000 SP4, same hardware.
In 5.2, the servers are in Windows 2003 SP1, same hardware.
The databases are the same.
Today, in my plan of migration, my masters are still in 5.1 and my consumers are in 5.2 and the problem of CPU load are only in 5.2.
I already add the nsslapd-search-tune to my dse.ldif, reindex the database, etc...but the performance are still the same.
When a request is done on the attribute uniquemember= "DN"...the response is too longer...
NPTa at 2007-7-12 14:54:55 >
