[
https://issues.apache.org/jira/browse/LUCENE-10636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17562464#comment-17562464
]
ASF subversion and git services commented on LUCENE-10636:
----------------------------------------------------------
Commit 2d05f5c623e06b8bafa1f7b1d6be813c14550690 in lucene's branch
refs/heads/branch_9x from Adrien Grand
[ https://gitbox.apache.org/repos/asf?p=lucene.git;h=2d05f5c623e ]
LUCENE-10636: Avoid computing the same scores multiple times. (#1005)
`BlockMaxMaxscoreScorer` would previously compute the score twice for essential
scorers.
Co-authored-by: zacharymorn <zacharym...@gmail.com>
> Could the partial score sum from essential list scores be cached?
> -----------------------------------------------------------------
>
> Key: LUCENE-10636
> URL: https://issues.apache.org/jira/browse/LUCENE-10636
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Zach Chen
> Priority: Minor
> Time Spent: 50m
> Remaining Estimate: 0h
>
> This is a follow-up issue from discussion
> [https://github.com/apache/lucene/pull/972#discussion_r909300200] . Currently
> in the implementation of BlockMaxMaxscoreScorer, there's duplicated
> computation of summing up scores from essential list scorers. We would like
> to see if this duplicated computation can be cached without introducing much
> overhead or data structure that might out-weight the benefit of caching.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
