[
https://issues.apache.org/jira/browse/LUCENE-5140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13722000#comment-13722000
]
Adrien Grand commented on LUCENE-5140:
--------------------------------------
I just tried to patch PhraseWeight but this doesn't make the query faster
according to lucenebench. I think it is normal given that that sort() is only
called when creating the scorer and not for every nextDoc() / advance() so it
shouldn't have an impact on the query throughput unless it is actually very
very slow? I also tried to run the benchmark under a profilter to see where
time is spent for phrase queries: the time spent in PhraseWeight.scorer is very
very small compared to scoring, and TimSorter.sort isn't even its bottleneck
(the bottleneck is the initialization of {{postingsFreqs}}).
> Slowdown of the span queries caused by LUCENE-4946
> --------------------------------------------------
>
> Key: LUCENE-5140
> URL: https://issues.apache.org/jira/browse/LUCENE-5140
> Project: Lucene - Core
> Issue Type: Bug
> Reporter: Adrien Grand
> Assignee: Adrien Grand
> Priority: Minor
> Attachments: LUCENE-5140.patch
>
>
> [~romseygeek] noticed that span queries have been slower since LUCENE-4946
> got committed.
> http://people.apache.org/~mikemccand/lucenebench/SpanNear.html
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
