[
https://issues.apache.org/jira/browse/LUCENE-5399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13908340#comment-13908340
]
ASF subversion and git services commented on LUCENE-5399:
---------------------------------------------------------
Commit 1570576 from [~martijn.v.groningen] in branch
'dev/branches/lucene_solr_4_7'
[ https://svn.apache.org/r1570576 ]
Fixed typo in CHANGES.txt for issue LUCENE-5399 and moved that issue under
optimizations.
> 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: 4.7, 5.0
>
> 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-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
