[ https://issues.apache.org/jira/browse/LUCENE-5140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Adrien Grand updated LUCENE-5140: --------------------------------- Attachment: LUCENE-5140.patch I think it is due to some overhead of our TimSorter implementation for small arrays. Here is a patch that replaces TimSorter with InPlaceMergeSorter, which should perform better on very small arrays but still has optimizations for sorted content, eg. merging two sorted slices is a no-op if the highest element from the 1st slice is lower than the least element from the 2nd slice. luceneutil seems to be happy with this patch (left is trunk, right is with patch applied): {noformat} LowSpanNear 143.65 (4.5%) 157.75 (3.9%) 9.8% ( 1% - 19%) HighSpanNear 5.47 (4.4%) 6.20 (9.7%) 13.4% ( 0% - 28%) MedSpanNear 94.27 (3.7%) 107.51 (3.7%) 14.1% ( 6% - 22%) {noformat} > 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org