[
https://issues.apache.org/jira/browse/LUCENE-2761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated LUCENE-2761:
--------------------------------
Attachment: LUCENE-2761.patch
same patch with an additional optimization from Mike.
||setup||run1||run2||run3||run4||run5||run6||
|LUCENE-2760+LUCENE-2761|6854|6874|6850|6855|6856|6846|
also, because we assume things about read/writeVint, i made these final in
DataInput.
I think we can use this same trick to speed up the terms dictionary, where it
scans past lots of useless vints/vlongs
> specialize payload processing from of DocsAndPositionsEnum
> ----------------------------------------------------------
>
> Key: LUCENE-2761
> URL: https://issues.apache.org/jira/browse/LUCENE-2761
> Project: Lucene - Java
> Issue Type: Improvement
> Reporter: Robert Muir
> Assignee: Robert Muir
> Fix For: 4.0
>
> Attachments: LUCENE-2761.patch, LUCENE-2761.patch, LUCENE-2761.patch
>
>
> In LUCENE-2760 i started working to try to improve the speed of a few
> spanqueries.
> In general the trick there is to avoid processing positions if you dont have
> to.
> But, we can improve queries that read lots of positions further by cleaning
> up SegmentDocsAndPositionsEnum,
> in nextPosition() this has no less than 3 payloads-related checks.
> however, a large majority of users/fields have no payloads at all.
> I think we should specialize this case into a separate implementation and
> speed up the common case.
> edit: dyslexia with the jira issue number.
--
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]
