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 2013/02/22 16:28:13 UTC
[jira] [Commented] (DIRSERVER-1808) We should evaluate the Scope
and any other index in a fliter only when the # of candidate is above a
threshold
[ https://issues.apache.org/jira/browse/DIRSERVER-1808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13584348#comment-13584348 ]
Emmanuel Lecharny commented on DIRSERVER-1808:
----------------------------------------------
I changed the evaluator method to stop evaluating & nodes as soon as we have a 0, and to avoid evaluating the scope node if the value is 1
The | node will stop evaluating as soon as the count is MAX_VALUE.
The scope node is moved to the end of the filter.
> We should evaluate the Scope and any other index in a fliter only when the # of candidate is above a threshold
> --------------------------------------------------------------------------------------------------------------
>
> Key: DIRSERVER-1808
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1808
> Project: Directory ApacheDS
> Issue Type: Improvement
> Affects Versions: 2.0.0-M10
> Reporter: Emmanuel Lecharny
> Fix For: 2.0.0-M11
>
>
> Currently, we evaluate *all* the nodes in a filter, regardless to the result of previous evaluation. It makes no sense to evaluate some & node if one node evaluates to 0 or 1. It makes no sense to evaluate some following nodes of a | node if one node evaluate to MAX.
> We could probably save a few CPU this way.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira