[
https://issues.apache.org/jira/browse/SOLR-8251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14997600#comment-14997600
]
Adrien Grand commented on SOLR-8251:
------------------------------------
bq. Maybe we should open a regression in Lucene core: Although FilteredQuery is
deprecated, I still think the rewrite of FilteredQuery(MatchAllDocs,Filter) ->
CSQ was perfectly fine. Not sure why Adrien Grand removed it in 5.x...
FilteredQuery was deprecated in favour of BooleanQuery so I wanted to make
FilteredQuery rewrite to the equivalent BooleanQuery to make things as close as
they will be in 6.0. The rewrite to a CSQ was fine indeed but instead of adding
back this optimization to FilteredQuery, I like Hoss' idea to add it to
BooleanQuery better as it would solve two issues at once given that
FilteredQuery already rewrites to a BooleanQuery?
> MatchAllDocsQuery is much slower in solr5.3.1 compare to solr4.7
> ----------------------------------------------------------------
>
> Key: SOLR-8251
> URL: https://issues.apache.org/jira/browse/SOLR-8251
> Project: Solr
> Issue Type: Bug
> Components: search
> Affects Versions: 5.3
> Reporter: wei shen
>
> I am trying to upgrade our production solr instance from 4.7 to 5.3.1.
> Unfortunately when I do load testing I find the MatchAllDocsQuery is much
> slower in solr 5.3.1 compare to 4.7. (solr 5.3.1 is faster in load test with
> queries other than MatchAllDocsQuery). I asked solr-user and discussed with
> Yonik Seeley. He confirmed that he can see the problem too comparing solr
> 5.3.1 and 4.10.
> here is the query I use:
> {code}
> q={!cache=false}*:*&fq=+categoryIdsPath:1001&fl=id&start=0&rows=2&debug=true
> {code}
> for me the query is consistently about 60-70% slower on solr5 than solr4.
> Yonik mentioned in his email "For me, 5.3.1
> is about 5x slower than 4.10 for this particular query."
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
