[
https://issues.apache.org/jira/browse/LUCENE-1483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12654842#action_12654842
]
Mark Miller commented on LUCENE-1483:
-------------------------------------
bq.I think there should be very little impact to performance, for single or
multi segment indices, for the search itself against a warmed reader. (And
actually LUCENE-1471 should make things a wee bit faster, especially if n,m are
largeish, though this will typically be in the noise).
That seems to be inline with what I got with 6 segments. I'm running some 30-50
seg range tests on my other laptop now.
bq. But warming after reopen should be much faster with this patch (we should
try to measure that too).
I've got a base alg for that type of thing around somewhere too, from 831. It
should be about the same, which means pretty dramatic reopen improvements if
you multiple segments, especially if the new segment is small. Its likely to be
small in comparison to all of the segs anyway, which means pretty great
improvements.
> Change IndexSearcher to use MultiSearcher semantics for sorted searches
> -----------------------------------------------------------------------
>
> Key: LUCENE-1483
> URL: https://issues.apache.org/jira/browse/LUCENE-1483
> Project: Lucene - Java
> Issue Type: Improvement
> Affects Versions: 2.9
> Reporter: Mark Miller
> Priority: Minor
> Attachments: LUCENE-1483.patch
>
>
> Here is a quick test patch. FieldCache for sorting is done at the individual
> IndexReader level and reloading the fieldcache on reopen can be much faster
> as only changed segments need to be reloaded.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
