[ https://issues.apache.org/jira/browse/LUCENE-8204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16555729#comment-16555729 ]
Jim Ferenczi commented on LUCENE-8204: -------------------------------------- Here is a patch that implements the block skipping logic. I had to modify the RandomApproximationQuery in the tests to make it compatible with advanceShallow. I also ran some benchmarks on wikimediumall, I used the HighLow, HighMed and HighHigh queries from the original benchmark and made the second clause optional to test this scorer: {noformat} TaskQPS lucene_baseline StdDevQPS lucene_candidate StdDev Pct diff HighMed 37.51 (0.0%) 38.05 (0.0%) 1.4% ( 1% - 1%) HighHigh 11.02 (0.0%) 16.47 (0.0%) 49.5% ( 49% - 49%) HighLow 103.91 (0.0%) 219.08 (0.0%) 110.8% ( 110% - 110%) {noformat} > ReqOptSumScorer should leverage sub scorers' per-block max scores > ----------------------------------------------------------------- > > Key: LUCENE-8204 > URL: https://issues.apache.org/jira/browse/LUCENE-8204 > Project: Lucene - Core > Issue Type: Improvement > Reporter: Adrien Grand > Priority: Minor > Attachments: LUCENE-8204.patch > > > Currently it only looks at max scores on the entire segment. Given that > per-block max scores usually give lower upper bounds of the score, this > should help. > This is especially important for LUCENE-8197 to work well since the main > query would typically be added as a MUST clauses of a boolean query while the > query that scores on features would be a SHOULD clause. -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org