[LUCENE-4100] Maxscore - Efficient Scoring

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 4.0-ALPHA
• Fix Version/s: 8.0
• Component/s: core/codecs, core/query/scoring, core/search
• Labels: api-change gsoc2014 patch performance
• Lucene Fields: New, Patch Available
• Assignee: Unassigned
• Reporter: Stefan Pohl
• Created: 02/Jun/12 15:38
• Updated: 28/Aug/22 13:18
• Resolved: 19/Dec/17 10:25

Description

At Berlin Buzzwords 2012, I will be presenting 'maxscore', an efficient algorithm first published in the IR domain in 1995 by H. Turtle & J. Flood, that I find deserves more attention among Lucene users (and developers).
I implemented a proof of concept and did some performance measurements with example queries and lucenebench, the package of Mike McCandless, resulting in very significant speedups.

This ticket is to get started the discussion on including the implementation into Lucene's codebase. Because the technique requires awareness about it from the Lucene user/developer, it seems best to become a contrib/module package so that it consciously can be chosen to be used.

Issue Links

• is related to: LUCENE-7996 Should we require positive scores?

Sub-Tasks

• Allow codecs to index term impacts: Closed