[
https://issues.apache.org/jira/browse/LUCENE-8448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16593405#comment-16593405
]
Dawid Weiss commented on LUCENE-8448:
-------------------------------------
Thank you for working on this, guys. I was on holidays and away from the world,
so couldn't provide feedback. Anyway, I still don't get the speedup on that
(synthetic) "benchmark" of mine; perhaps it's because I'm using min should
match (?):
{code}
BooleanQuery.Builder qb = new BooleanQuery.Builder();
for (int k = 0; k < clausesPerQuery; k++) {
BooleanQuery.Builder cb = new BooleanQuery.Builder();
String term = randomFrom(rnd, terms);
for (String fld : fields) {
cb.add(new TermQuery(new Term(fld, term)), Occur.SHOULD);
}
qb.add(cb.build(), Occur.SHOULD);
}
qb.setMinimumNumberShouldMatch(1);
{code}
Like I told Adrien, this isn't critical and definitely not typical (for
humans), but the performance dropped twice for me on this type of queries
compared to what it was previously.
> Slowdown of nested boolean queries after LUCENE-8060
> ----------------------------------------------------
>
> Key: LUCENE-8448
> URL: https://issues.apache.org/jira/browse/LUCENE-8448
> Project: Lucene - Core
> Issue Type: Task
> Reporter: Adrien Grand
> Priority: Minor
> Fix For: master (8.0)
>
> Attachments: LUCENE-8448.patch, LUCENE-8448.patch
>
>
> Mike's nightly benchmarks revealed that disabling hit counts slowed down
> nested boolean queries
> http://people.apache.org/~mikemccand/lucenebench/AndHighOrMedMed.html
> http://people.apache.org/~mikemccand/lucenebench/AndMedOrHighHigh.html.
> We are probably not propagating max scores and/or blocks efficiently.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
