Uploaded image for project: 'Lucene - Core'
  1. Lucene - Core
  2. LUCENE-10367

Use WANDScorer in CoveringQuery Can accelerate scorer time

Details

    • New
    • Yes

    Description

      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. 

      Attachments

        1. TestCoveringQueryBench.java
          4 kB
          LuYunCheng
        2. LUCENE-10367.patch
          9 kB
          LuYunCheng

        Activity

          People

            Unassigned Unassigned
            luyuncheng LuYunCheng
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: