directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Emmanuel Lecharny (JIRA)" <j...@apache.org>
Subject [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
Date Sat, 23 Feb 2013 13:46:12 GMT

    [ https://issues.apache.org/jira/browse/DIRSERVER-1808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13585117#comment-13585117
] 

Emmanuel Lecharny commented on DIRSERVER-1808:
----------------------------------------------

The (ObjectClass=*) node is now removed from the filter : it's useless.
                
> 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

Mime
View raw message