directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Emmanuel Lecharny (JIRA)" <>
Subject [jira] Commented: (DIRSERVER-1051) Avoid a lookup in CollectiveAttributeService
Date Fri, 21 Sep 2007 21:52:50 GMT


Emmanuel Lecharny commented on DIRSERVER-1051:

The issue has been partially fixed. If the request contains no requested attributes, then
no lookup is done to add the collective attribute. For some deep reasons (buried into the
way the Partition is implemented), we can't avoid a lookup in any other case.

However, in normal case, the server is now 7% faster. (up from 4500 req/s to 4800 req/s)

> Avoid a lookup in CollectiveAttributeService
> --------------------------------------------
>                 Key: DIRSERVER-1051
>                 URL:
>             Project: Directory ApacheDS
>          Issue Type: Improvement
>    Affects Versions: 1.5.1
>            Reporter: Emmanuel Lecharny
>             Fix For: 2.0.0
> To process collectiveAttributes, the service does a lookup searcing for the "collectiveAttributeSubentries"
operational attribute. This lookup cost around 17% of the global search time, and can be avoided,
as we can add this attribute to the list of returned attribute in the original lookup, instead
of doing a specific lookup for this attribute.
> We have two cases :
> - the "collectiveAttributeSubentries" does not exist : net gain will be 17%
> - the "collectiveAttributeSubentries" exists : we will have to remove it from the entry
and process the collective attributes to add them to the entry. The gain will still be enormous
(less than 17%, but very close)
> In the second case, we will just have to be sure to return this attrinute to the user
who has specifically requested it into the original search request.
> The gain will be major.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message