directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Siva Kumar" <>
Subject RE: Searching takes unrealistic time.
Date Fri, 25 Jan 2008 13:14:10 GMT
Thank you for the tip Emmanuel.

But its not seem to help me.


I have a custom schema and partition created in ADS and the 40K entries I mentioned follows
the custom objectClass definition.(below)

objectClass (
	NAME 'mbxperson'
	MUST ( uid $ cn $ gn $ sn $ telephoneNumber )
	MAY ( mobileNumber $ ou $ primaryExtention $ title )
	X-ORIGIN 'user defined' )

I have attached the server.xml also for your reference.

My searches are based on names,primaryExtention and telephoneNumber. The performance looks
the same as when no indexes specified.

I have even wiped the whole data off and recreated the entries again to make sure the indexes
applied correctly.

Am I missing anything in the loop in this process? Is there any step I missed out completely??

It would be great if you could help?

Thanks in advance.


-----Original Message-----
From: Emmanuel Lecharny [] 
Sent: 24 January 2008 16:06
To: Apache Directory Developers List
Subject: Re: Searching takes unrealistic time.

Siva Kumar wrote:
>         <bean
> class="
> de
> xConfiguration">
>           <property name="attributeId" value="uid" />
>           <property name="cacheSize" value="100" />
Considering you are using the uid attribute, with 40 000 entries in your base, the current
cacheSize will hold 0,25% of the existing uid. That means you are roughly doing a disk access
each time you search for an entry.

Increase the cacheSize for each attribute your filters are using. Here, 40 000 will be ok.

Be aware that you may have to increase the JVM memory size to avoid OOM exception too...

Hope it helps

cordialement, regards,
Emmanuel L├ęcharny

View raw message