[
https://issues.apache.org/jira/browse/LUCENE-8340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16602715#comment-16602715
]
Jim Ferenczi commented on LUCENE-8340:
--------------------------------------
nice speed up, +1
{quote}If I switch to more costly queries that have fewer hits then the speed
up decreases, or even becomes a slowdown unfortunately.{quote}
We could add a penalty to the estimated count of the point visitor when it is
compared with the leadCost or check the difference between the max scores of
the other clauses and the max score of the distance query ? Since we can skip
blocks in the parent scorer (reqOptSumScorer) I guess we can be less aggressive
when applying the point visitor optimization.
> Efficient boosting by recency
> -----------------------------
>
> Key: LUCENE-8340
> URL: https://issues.apache.org/jira/browse/LUCENE-8340
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Adrien Grand
> Priority: Minor
> Attachments: LUCENE-8340.patch
>
>
> I would like that we support something like
> \{{FeatureField.newSaturationQuery}} but that works with features that are
> computed dynamically like recency or geo-distance, and is still optimized for
> top-hits collection. I'm starting with recency because it makes things a bit
> easier even though I suspect that geo-distance might be a more common need.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
