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

Robert Muir commented on LUCENE-6198:
-------------------------------------

{quote}
Or maybe we simply disallow recursive approximations for starters? I do like 
that the current patch is a baby step that looks like it can succeed
{quote}

its not clear at all that this complicated stuff you guys propose would even 
help. 

The current patch passes all tests and i sat alongside luceneutil benchmark 
making it. Please dont underestimate how annoying it is to change the code in 
any way without pissing that thing off brutally.

I don't think we should try to do complicated things all at once. At least i 
won't be the one doing it. Its gotta be realistic: and its gotta have realistic 
goals. 

Plain and simple: speed up the proximity queries. I'm not trying to speed up 
advance(). Leave that for another issue, plenty of time has been wasted on that 
before.

> two phase intersection
> ----------------------
>
>                 Key: LUCENE-6198
>                 URL: https://issues.apache.org/jira/browse/LUCENE-6198
>             Project: Lucene - Core
>          Issue Type: Improvement
>            Reporter: Robert Muir
>         Attachments: LUCENE-6198.patch
>
>
> Currently some scorers have to do a lot of per-document work to determine if 
> a document is a match. The simplest example is a phrase scorer, but there are 
> others (spans, sloppy phrase, geospatial, etc).
> Imagine a conjunction with two MUST clauses, one that is a term that matches 
> all odd documents, another that is a phrase matching all even documents. 
> Today this conjunction will be very expensive, because the zig-zag 
> intersection is reading a ton of useless positions.
> The same problem happens with filteredQuery and anything else that acts like 
> a conjunction.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to