You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Michael McCandless (JIRA)" <ji...@apache.org> on 2014/01/16 20:03:22 UTC
[jira] [Resolved] (LUCENE-5399) PagingFieldCollector is very slow
with String fields
[ https://issues.apache.org/jira/browse/LUCENE-5399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael McCandless resolved LUCENE-5399.
----------------------------------------
Resolution: Fixed
Fix Version/s: 4.7
5.0
> PagingFieldCollector is very slow with String fields
> ----------------------------------------------------
>
> Key: LUCENE-5399
> URL: https://issues.apache.org/jira/browse/LUCENE-5399
> Project: Lucene - Core
> Issue Type: Bug
> Components: core/search
> Reporter: Robert Muir
> Fix For: 5.0, 4.7
>
> Attachments: LUCENE-5399.patch, LUCENE-5399.patch, LUCENE-5399.patch, LUCENE-5399.patch, LUCENE-5399.patch, LUCENE-5399.patch, LUCENE-5399.patch, LUCENE-5399.patch, LUCENE-5399.patch
>
>
> PagingFieldCollector (sort comparator) is significantly slower with string fields, because of how its "seen on a previous page" works: it calls compareDocToValue(int doc, T t) first to check this. (its the only user of this method)
> This is very slow with String, because no ordinals are used. so each document must lookup ord, then lookup bytes, then compare bytes.
> I think maybe we should replace this method with an 'after' slot, and just have compareDocToAfter or something.
> Otherwise we could use a hack-patch like the one i will upload (i did this just to test the performance, although tests do pass).
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org