jpountz commented on PR #14968: URL: https://github.com/apache/lucene/pull/14968#issuecomment-3168139999
Another idea: in order to not add new APIs, an alternative would be to implement specialized bulk scorers for the case when all scorers are term scorers, on the same field (a common case, and arguably the case we're most interested in optimizing) and work directly on `ImpactsEnum`, norms, and `SimScorer`. This should allow us to do interesting things without introducing new APIs, such as reading norms only once per doc ID or vectorizing score computations of required/non-essential clauses. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
