directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Karasulu (JIRA)" <j...@apache.org>
Subject [jira] Closed: (DIRSERVER-1051) Avoid a lookup in CollectiveAttributeService
Date Thu, 21 Aug 2008 04:30:44 GMT

     [ https://issues.apache.org/jira/browse/DIRSERVER-1051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Alex Karasulu closed DIRSERVER-1051.
------------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: 2.0.0)
                   1.5.4

I think we fixed this overhead.

> Avoid a lookup in CollectiveAttributeService
> --------------------------------------------
>
>                 Key: DIRSERVER-1051
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-1051
>             Project: Directory ApacheDS
>          Issue Type: Improvement
>    Affects Versions: 1.5.1
>            Reporter: Emmanuel Lecharny
>            Assignee: Alex Karasulu
>             Fix For: 1.5.4
>
>
> 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.


Mime
View raw message