[ 
https://issues.apache.org/jira/browse/LUCENE-4100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16136601#comment-16136601
 ] 

Adrien Grand commented on LUCENE-4100:
--------------------------------------

bq. how to safely implement the optimization for dynamic indexes: See Stefan's 
note above. I do agree there are use cases for static indexes, the problem is: 
its lucene, people will try to use it with dynamic indexes regardless

Maybe BM25 is making our lives easier with this? Scores are bounded by {{IDF * 
(k1 + 1)}} if I'm not mistaken so we could use it to feed the MAXSCORE 
algorithm? It would not be as good as the initial patch since we are totally 
ignoring the range of values that the term frequency and document length may 
take but this would not require any index-time changes, does not require the 
index to be static and might already allow for good speedups if query terms 
have very different IDF values?



> Maxscore - Efficient Scoring
> ----------------------------
>
>                 Key: LUCENE-4100
>                 URL: https://issues.apache.org/jira/browse/LUCENE-4100
>             Project: Lucene - Core
>          Issue Type: Improvement
>          Components: core/codecs, core/query/scoring, core/search
>    Affects Versions: 4.0-ALPHA
>            Reporter: Stefan Pohl
>              Labels: api-change, gsoc2014, patch, performance
>             Fix For: 4.9, 6.0
>
>         Attachments: contrib_maxscore.tgz, maxscore.patch
>
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to