You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Emmanuel Lecharny (JIRA)" <ji...@apache.org> on 2007/08/31 15:22:31 UTC
[jira] Created: (DIRSERVER-1051) Avoid a lookup in
CollectiveAttributeService
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
Fix For: 1.5.2
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.
[jira] Updated: (DIRSERVER-1051) Avoid a lookup in
CollectiveAttributeService
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny updated DIRSERVER-1051:
-----------------------------------------
Fix Version/s: (was: 1.5.2)
2.0.0
Moved to 2.0, because for a complete fix, it is necessary to modify the Partition subsystem
> 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
> 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.
[jira] Assigned: (DIRSERVER-1051) Avoid a lookup in
CollectiveAttributeService
Posted by "Alex Karasulu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Karasulu reassigned DIRSERVER-1051:
----------------------------------------
Assignee: Alex Karasulu
> 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.
[jira] Commented: (DIRSERVER-1051) Avoid a lookup in
CollectiveAttributeService
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12529562 ]
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: https://issues.apache.org/jira/browse/DIRSERVER-1051
> 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.
[jira] Closed: (DIRSERVER-1051) Avoid a lookup in
CollectiveAttributeService
Posted by "Alex Karasulu (JIRA)" <ji...@apache.org>.
[ 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.