You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Adrien Grand (JIRA)" <ji...@apache.org> on 2016/03/03 14:58:18 UTC
[jira] [Commented] (LUCENE-7051) Remove the "estimate match count"
optimization from point queries
[ https://issues.apache.org/jira/browse/LUCENE-7051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15177832#comment-15177832 ]
Adrien Grand commented on LUCENE-7051:
--------------------------------------
bq. I'll watch http://home.apache.org/~mikemccand/lucenebench/IntNRQ.html in the coming days to make sure the nightly benchmarks agree this optimization was not necessary.
The last point onthe chart from march 1st looks good so I think we're fine.
> Remove the "estimate match count" optimization from point queries
> -----------------------------------------------------------------
>
> Key: LUCENE-7051
> URL: https://issues.apache.org/jira/browse/LUCENE-7051
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Adrien Grand
> Assignee: Adrien Grand
> Priority: Minor
> Fix For: 6.0
>
> Attachments: LUCENE-7051.patch
>
>
> Point queries try to estimate the number of matches in the visitor so that the doc id set that they build does not have to do it by itself. However, this is incorrect in the multi-valued case and does not seem to buy much (if any) in terms of performance?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org