lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (LUCENE-7262) Add back the "estimate match count" optimization
Date Mon, 02 May 2016 14:16:12 GMT


ASF subversion and git services commented on LUCENE-7262:

Commit e9f2ac0021e004593599706f4e2db1bd1f724248 in lucene-solr's branch refs/heads/branch_6x
from [~jpountz]
[;h=e9f2ac0 ]

LUCENE-7262: Leverage index statistics to make DocIdSetBuilder more efficient.

> Add back the "estimate match count" optimization
> ------------------------------------------------
>                 Key: LUCENE-7262
>                 URL:
>             Project: Lucene - Core
>          Issue Type: Improvement
>            Reporter: Adrien Grand
>            Assignee: Adrien Grand
>            Priority: Minor
>             Fix For: master, 6.1
>         Attachments: LUCENE-7262.patch, LUCENE-7262.patch, LUCENE-7262.patch
> Follow-up to my last message on LUCENE-7051: I removed this optimization a while ago
because it made things a bit more complicated but did not seem to help with point queries.
However the reason why it did not seem to help was that the benchmark only runs queries that
match 25% of the dataset. This makes the run time completely dominated by calls to FixedBitSet.set
so the call to FixedBitSet.cardinality() looks free. However with slightly sparser queries
like the geo benchmark generates (dense enough to trigger the creation of a FixedBitSet but
sparse enough so that FixedBitSet.set does not dominate the run time), one can notice speed-ups
when this call is skipped.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message