You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Jim Ferenczi (JIRA)" <ji...@apache.org> on 2017/08/23 15:55:00 UTC
[jira] [Commented] (LUCENE-7939) Speed up MinShouldMatchSumScorer
in conjunctions
[ https://issues.apache.org/jira/browse/LUCENE-7939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16138532#comment-16138532 ]
Jim Ferenczi commented on LUCENE-7939:
--------------------------------------
Very impressive results ! The impacts when there is no conjunction are not significant so big +1.
> Speed up MinShouldMatchSumScorer in conjunctions
> ------------------------------------------------
>
> Key: LUCENE-7939
> URL: https://issues.apache.org/jira/browse/LUCENE-7939
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Adrien Grand
> Priority: Minor
> Fix For: master (8.0), 7.1
>
> Attachments: LUCENE-7939.patch, LUCENE-7939.patch
>
>
> MinShouldMatchSumScorer has good iteration capabilities, but if it is not used as a lead for the iteration then the advance() call might make a lot of efforts in order to find the next match while we should instead let the lead iterator of the conjunction skip over non-matching documents. In this issue I'd like to explore changing MinShouldMatchSumScorer by giving it a two-phase iterator and making advance() return a candidate for the next match that is less good but much cheaper to compute.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org