[
https://issues.apache.org/jira/browse/LUCENE-8770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16844612#comment-16844612
]
Jim Ferenczi commented on LUCENE-8770:
--------------------------------------
{quote}
I wonder how useful computing the score in the two-phase and the iterator help
now, can we get rid of it or would it hurt?
{quote}
I think we can, I ran the benchmark without the score check in the iterator and
here's the result:
{noformat}
TaskQPS baseline StdDev QPS patch StdDev
Pct diff
AndHighMed 58.08 (4.9%) 54.60 (11.0%)
-6.0% ( -20% - 10%)
AndHighHigh 23.08 (7.5%) 22.64 (12.1%)
-1.9% ( -19% - 19%)
AndHighLow 427.13 (4.7%) 434.58 (10.5%)
1.7% ( -12% - 17%)
{noformat}
> BlockMaxConjunctionScorer should support two-phase scorers
> ----------------------------------------------------------
>
> Key: LUCENE-8770
> URL: https://issues.apache.org/jira/browse/LUCENE-8770
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Jim Ferenczi
> Priority: Minor
> Attachments: LUCENE-8770.patch
>
>
> The support for two-phase scorers in BlockMaxConjunctionScorer is missing.
> This can slow down some queries that need to execute costly second phase on
> more documents.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
