[
https://issues.apache.org/jira/browse/LUCENE-7199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15234120#comment-15234120
]
Michael McCandless commented on LUCENE-7199:
--------------------------------------------
Indeed it's much faster! Now it's:
{noformat}
24.8 QPS (9.1 sec for 225 queries), totHits=355855224
{noformat}
for not-pre-built queries. If I pre-build I get:
{noformat}
25.3 QPS (8.9 sec for 225 queries), totHits=355855224
{noformat}
So only a slight gain (possibly within noise) for pre-built queries now!
> Improve algorithm for randomly finding an interior point for Geo3D polygons
> ---------------------------------------------------------------------------
>
> Key: LUCENE-7199
> URL: https://issues.apache.org/jira/browse/LUCENE-7199
> Project: Lucene - Core
> Issue Type: Improvement
> Components: modules/spatial3d
> Affects Versions: master
> Reporter: Karl Wright
> Assignee: Karl Wright
> Fix For: master, 6.x
>
>
> [~mikemccand]'s benchmark for polygon search shows that constructing Geo3D
> polygon queries is quite expensive compared to other technologies. My belief
> is that this is due largely to how an interior point for determination of
> clockwise/counterclockwise are found: this is currently searched for randomly
> across the entire globe.
> I suspect that we could replace this algorithm with a random algorithm that
> uses one of the polygon's edge points and looks randomly within a small
> distance of that point. This would greatly reduce the number of failed
> attempts to find a "pole" (as I call it).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]