You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Robert Muir (JIRA)" <ji...@apache.org> on 2010/11/15 16:34:15 UTC

[jira] Updated: (LUCENE-2761) specialize payload processing from of DocsAndPositionsEnum

     [ https://issues.apache.org/jira/browse/LUCENE-2761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Muir updated LUCENE-2761:
--------------------------------

    Description: 
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.

  was:
In LUCENE-2670 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.



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