[
https://issues.apache.org/jira/browse/DIRAPI-7?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12864333#action_12864333
]
Pierre-Arnaud Marcelot commented on DIRAPI-7:
---------------------------------------------
Hi guys,
I've just re-run the test and indeed there seem to be a problem with logs.
When I launch it without configuring the logs, the LDAP Client API is two times
slower than JNDI (9000ms compared to 4200ms), but when I launch it with logs
configured to OFF, then the LDAP Client API is almost as the same level of
performance as JNDI (4400ms compared to 4200ms).
It would be better if the logs could be set to OFF is they are not configured,
because I'm almost sure 99% of the users won't configure them.
> Low performance on search operation compared to JNDI (around 5 times slower)
> ----------------------------------------------------------------------------
>
> Key: DIRAPI-7
> URL: https://issues.apache.org/jira/browse/DIRAPI-7
> Project: Directory client API
> Issue Type: Bug
> Reporter: Pierre-Arnaud Marcelot
> Priority: Critical
> Fix For: 0.2.0
>
> Attachments: base.ldif, TestWithClientApi.java, TestWithJndi.java
>
>
> While playing with the Client API, I compared the performance of the same
> search to JNDI.
> With current code, the Client API is unfortunately 5 times slower.
> My test is pretty simple, I'm searching with a Subtree scope on
> 'dc=example,dc=com' partition which holds 10 000 users.
> Here are the results:
> - JNDI:
> Time to create the connection: 90
> Time to perform the search: 4195
> Time to close the connection: 1
> Total time: 4286
> -Client API:
> Time to create the connection: 399
> Time to perform the search: 23417
> Time to close the connection: 33
> Total time: 23849
> Time is expressed as milliseconds.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
