[
https://issues.apache.org/jira/browse/LUCENE-2694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12972758#action_12972758
]
Michael McCandless commented on LUCENE-2694:
--------------------------------------------
If I force scoring BQ rewrite for wildcard & prefix queries (ie set that
rewrite mode and then relax BQ max clause count) I see healthy speedups
(~23-27%) for these queries! Great :)
While this doesn't happen w/ our default settings (ie these queries quickly
cutover to constant filter rewrite), apps that change these defaults will see a
gain, plus, the term cache (which today "protects" you) is terribly fragile
since apps w/ many MTQ queries in flight can thrash that cache thus killing
performance. This patch prevents that entirely since MTQs do their own caching
of the TermStates they need: awesome.
> MTQ rewrite + weight/scorer init should be single pass
> ------------------------------------------------------
>
> Key: LUCENE-2694
> URL: https://issues.apache.org/jira/browse/LUCENE-2694
> Project: Lucene - Java
> Issue Type: Improvement
> Components: Search
> Reporter: Michael McCandless
> Assignee: Michael McCandless
> Fix For: 4.0
>
> Attachments: LUCENE-2694.patch, LUCENE-2694.patch, LUCENE-2694.patch,
> LUCENE-2694.patch
>
>
> Spinoff of LUCENE-2690 (see the hacked patch on that issue)...
> Once we fix MTQ rewrite to be per-segment, we should take it further and make
> weight/scorer init also run in the same single pass as rewrite.
--
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]
