You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Robert Muir (JIRA)" <ji...@apache.org> on 2016/04/13 21:28:25 UTC
[jira] [Commented] (LUCENE-7214) Remove two-phase iteration from
LatLonPoint.newDistanceQuery
[ https://issues.apache.org/jira/browse/LUCENE-7214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15239901#comment-15239901 ]
Robert Muir commented on LUCENE-7214:
-------------------------------------
2D distance with no filter: 22.1 QPS -> 33.5 QPS
2D distance with 100% filter: 16.0 QPS -> 23.4 QPS
2D distance with 10% filter: 24.1 QPS -> 25.1 QPS
2D distance with 1% filter: 42.7 QPS -> 42.1 QPS
2D distance with 0.1% filter: 51.1 QPS -> 48.9 QPS
2D distance with 0.0001% filter: 55.7 QPS -> 52.6 QPS
> Remove two-phase iteration from LatLonPoint.newDistanceQuery
> ------------------------------------------------------------
>
> Key: LUCENE-7214
> URL: https://issues.apache.org/jira/browse/LUCENE-7214
> Project: Lucene - Core
> Issue Type: Bug
> Reporter: Robert Muir
>
> This was a nice crutch for tons of expensive per-document methods, but its no longer needed anymore. After LUCENE-7147 these are truly only boundary cases and we aren't doing a ton of per doc checks anymore. See LUCENE-7212 for inspiration.
> The extra bitset needed, 64-bit docvalues fetch, etc, this cost is no longer worth it.
--
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