lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hoss Man (JIRA)" <j...@apache.org>
Subject [jira] [Created] (LUCENE-7618) Hypothetical perf improvements in DocValuesRangeQuery: reducing comparisons for some queries/segments
Date Tue, 03 Jan 2017 21:20:58 GMT
Hoss Man created LUCENE-7618:
--------------------------------

             Summary: Hypothetical perf improvements in DocValuesRangeQuery: reducing comparisons
for some queries/segments
                 Key: LUCENE-7618
                 URL: https://issues.apache.org/jira/browse/LUCENE-7618
             Project: Lucene - Core
          Issue Type: Improvement
            Reporter: Hoss Man



In reviewing the DocValuesRangeQuery code, it occured to me that there _might_ be some potential
performance optimizations possible in a few cases relating queries that involve explicitly
specified open ranges (ie: min or max are null) or in the case of SortedSet: range queries
that are *effectively* open ended on particular segments, because the min/max are below/above
the minOrd/maxOrd for the segment.

Since these seemed like semi-common situations (open ended range queries are fairly common
in my experience, i'm not sure about the secondary SortedSet "ord" case, but it seemd potentially
promising particularly for fields like incrementing ids, or timestamps, where values are added
sequentially and likeley to be clustered together) I did a bit of experimenting and wanted
to post my findings in jira -- patch & details to follow in comments.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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


Mime
View raw message