You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "LuYunCheng (Jira)" <ji...@apache.org> on 2022/02/08 06:19:00 UTC
[jira] [Updated] (LUCENE-10367) Use WANDScorer in CoveringQuery Can accelerate scorer time
[ https://issues.apache.org/jira/browse/LUCENE-10367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
LuYunCheng updated LUCENE-10367:
--------------------------------
Status: Open (was: Patch Available)
> Use WANDScorer in CoveringQuery Can accelerate scorer time
> ----------------------------------------------------------
>
> Key: LUCENE-10367
> URL: https://issues.apache.org/jira/browse/LUCENE-10367
> Project: Lucene - Core
> Issue Type: Improvement
> Components: core/query/scoring, core/search, modules/sandbox
> Reporter: LuYunCheng
> Priority: Major
> Attachments: LUCENE-10367.patch, TestCoveringQueryBench.java
>
>
> When using CoveringQuery In Elasticsearch with terms_set query, it takes too much time in CoveringScore and major cost in matain the DisiPriorityQueue: subScorers.
> But when minimumNumberMatch is ConstantLongValuesSource, we can use WANDScorer to optimize it.
>
> i do a mini benchmark with 1m docs, which code in LUCENE-10367.patch TestCoveringQuery.java testRandomBench()
> it shows:
> TEST: WAND elapsed 67ms
> TEST: NOWAND elapsed 163ms
> My testing environment is macBook with Intel Core i7 16GMem.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org