[
https://issues.apache.org/jira/browse/LUCENE-3664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13556328#comment-13556328
]
Simon Willnauer commented on LUCENE-3664:
-----------------------------------------
hey john,
I agree this could safe a bunch of checks along the lines. For heavy queries
this could be problematic ie phrases would check way more docs than needed if
the live docs is very sparse. I think we should have it in both places but
making it optional where to do it is an interesting idea. Depending on the
cardinality we could do the checks in the IndexSearcher or rather in the top
level collect method or in the Collector.
> Speed up SegementDocsAndPositionsEnum by making it more friendly for JIT
> optimizations
> --------------------------------------------------------------------------------------
>
> Key: LUCENE-3664
> URL: https://issues.apache.org/jira/browse/LUCENE-3664
> Project: Lucene - Core
> Issue Type: Improvement
> Components: core/search
> Affects Versions: 4.0-ALPHA
> Reporter: Simon Willnauer
> Priority: Minor
> Fix For: 4.2, 5.0
>
> Attachments: LUCENE-3664.patch
>
>
> LUCENE-3648 applied some refactoring to make SegmentDocsEnum reuse some code
> and divorce the liveDocs and no-liveDocs case into sep classes to make more
> friendly for jit optimizations. I did the same thing for
> SegmentDocsAndPositions[AndPayloads]Enum removing a couple of hundred lines
> of code abstracting it into a base class. patch follows in a sec...
--
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: [email protected]
For additional commands, e-mail: [email protected]
