lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Miller (JIRA)" <j...@apache.org>
Subject [jira] Issue Comment Edited: (LUCENE-1483) Change IndexSearcher multisegment searches to search each individual segment using a single HitCollector
Date Wed, 14 Jan 2009 03:04:59 GMT

    [ https://issues.apache.org/jira/browse/LUCENE-1483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12663607#action_12663607
] 

markrmiller@gmail.com edited comment on LUCENE-1483 at 1/13/09 7:03 PM:
--------------------------------------------------------------

Disregarding any missing gains with those simple policies, the rest of those numbers actually
look pretty good! Still some problems here and there (large queue size still sticky), but
overall some solid gains as well.

orddem seems to be best in most cases currently - maybe we can tweak that a little more somehow.
Where its not better, or not much worse, is with a single segment. That result is interesting,
because both policies beat it nicely, and its because they simpely use straight ord on the
first segment. But ordsubord seems to outperform the policies. That doesn't make sense. Its
largely the same, but should be a tad slower if anything. Other results match up so nicely,
it seems like it might not be noise, in which case, weird.

      was (Author: markrmiller@gmail.com):
    Disregarding any any with those simple policies, the rest of those numbers actually look
pretty good! Still some problems here and there (large queue size still sticky), but overall
some solid gains as well.

orddem seems to be best in most cases currently - maybe we can tweak that a little more somehow.
Where its not better, or not much worse, is with a single segment. That result is interesting,
because both policies beat it nicely, and its because they simple use straight ord on the
first segment. But ordsubord seems to outperform the policies. That doesn't make sense. Its
largely the same, but should be a tad slower if anything. Other results match up so nicely,
it seems like it might not be noise, in which case, weird.
  
> Change IndexSearcher multisegment searches to search each individual segment using a
single HitCollector
> --------------------------------------------------------------------------------------------------------
>
>                 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-partial.patch, LUCENE-1483.patch, LUCENE-1483.patch,
LUCENE-1483.patch, LUCENE-1483.patch, LUCENE-1483.patch, LUCENE-1483.patch, LUCENE-1483.patch,
LUCENE-1483.patch, LUCENE-1483.patch, LUCENE-1483.patch, LUCENE-1483.patch, LUCENE-1483.patch,
LUCENE-1483.patch, LUCENE-1483.patch, LUCENE-1483.patch, LUCENE-1483.patch, LUCENE-1483.patch,
LUCENE-1483.patch, LUCENE-1483.patch, LUCENE-1483.patch, LUCENE-1483.patch, LUCENE-1483.patch,
LUCENE-1483.patch, LUCENE-1483.patch, LUCENE-1483.patch, LUCENE-1483.patch, sortBench.py,
sortCollate.py
>
>
> FieldCache and Filters are forced down to a single segment reader, allowing for individual
segment reloading on reopen.

-- 
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: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org


Mime
View raw message