lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Uwe Schindler (JIRA)" <>
Subject [jira] [Commented] (LUCENE-3328) Specialize BooleanQuery if all clauses are TermQueries
Date Sun, 24 Jul 2011 10:14:09 GMT


Uwe Schindler commented on LUCENE-3328:

Indeed breaks in Java are no real gotos. The label must always be placed *before* the loop
that you want to break out (it would give syntax error otherwise). In fact it simply exits
the loop to this level and proceeds working *after* the loop. A simple break without a label
is identical to a non-hierarchical loop with a autogenerated label in front of it.

> Specialize BooleanQuery if all clauses are TermQueries
> ------------------------------------------------------
>                 Key: LUCENE-3328
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: core/search
>    Affects Versions: 3.4, 4.0
>            Reporter: Simon Willnauer
>            Assignee: Simon Willnauer
>             Fix For: 4.0
>         Attachments: LUCENE-3328.patch, LUCENE-3328.patch, LUCENE-3328.patch
> During work on LUCENE-3319 I ran into issues with BooleanQuery compared to PhraseQuery
in the exact case. If I disable scoring on PhraseQuery and bypass the position matching, essentially
doing a conjunction match, ExactPhraseScorer beats plain boolean scorer by 40% which is a
sizeable gain. I converted a ConjunctionScorer to use DocsEnum directly but still didn't get
all the 40% from PhraseQuery. Yet, it turned out with further optimizations this gets very
close to PhraseQuery. The biggest gain here came from converting the hand crafted loop in
ConjunctionScorer#doNext to a for loop which seems to be less confusing to hotspot. In this
particular case I think code specialization makes lots of sense since BQ with TQ is by far
one of the most common queries.
> I will upload a patch shortly

This message is automatically generated by JIRA.
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message