You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Adrien Grand (JIRA)" <ji...@apache.org> on 2017/01/26 14:58:24 UTC

[jira] [Updated] (LUCENE-7660) LatLonPointDistanceQuery could skip distance computations more often

     [ https://issues.apache.org/jira/browse/LUCENE-7660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Adrien Grand updated LUCENE-7660:
---------------------------------
    Attachment: LUCENE-7660.patch

Here is a patch. The {{IndexAndSearchOpenstreetMaps}} benchmark as-is does not show any change in QPS, which is expected since it only indexes points and performs queries around London, so at least this change is not making things slower. But I hacked the benchmark to add 180 to all longitudes in documents/queries and the QPS went from 17 to 39 with this patch.

> LatLonPointDistanceQuery could skip distance computations more often
> --------------------------------------------------------------------
>
>                 Key: LUCENE-7660
>                 URL: https://issues.apache.org/jira/browse/LUCENE-7660
>             Project: Lucene - Core
>          Issue Type: Improvement
>            Reporter: Adrien Grand
>            Priority: Minor
>         Attachments: LUCENE-7660.patch
>
>
> Currently the logic that check whether all points of a box are within the circle does not take longitude wrapping into account. As a consequence, if you run a distance query whose circle crosses the dateline, we might be performing LOTs of distance computations.



--
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