[
https://issues.apache.org/jira/browse/LUCENE-8928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16950858#comment-16950858
]
Adrien Grand commented on LUCENE-8928:
--------------------------------------
The nightly benchmarks liked this change
http://people.apache.org/~mikemccand/geobench.html
- 32% faster distance filtering with Geo3D
- 38% faster 10-gons filtering with Geo3D
- 20% faster 10-gons filtering with shapes
- 30% faster box filtering with Geo3D
- 22% faster box filtering with shapes
- 1% space reduction for shapes
However
- ~7% slower indexing for Geo3D
- ~8% slower indexing for shapes
> BKDWriter could make splitting decisions based on the actual range of values
> ----------------------------------------------------------------------------
>
> Key: LUCENE-8928
> URL: https://issues.apache.org/jira/browse/LUCENE-8928
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Adrien Grand
> Priority: Minor
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Currently BKDWriter assumes that splitting on one dimension has no effect on
> values in other dimensions. While this may be ok for geo points, this is
> usually not true for ranges (or geo shapes, which are ranges too). Maybe we
> could get better indexing by re-computing the range of values on each
> dimension before making the choice of the split dimension?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
