Anecdotal evidence that useFilterForSortedQuery has gotten much slower in 3.5
compared to 1.4
---------------------------------------------------------------------------------------------
Key: SOLR-2944
URL: https://issues.apache.org/jira/browse/SOLR-2944
Project: Solr
Issue Type: Bug
Reporter: Hoss Man
Pawel Rog reported on the user list that he was seeing significantly slower
search performance and much higher CPU usage using Solr 3.5 compared to Solr
1.4 when using the same configs he had always used in Solr 1.4 -- even though
he had a new index built with 3.5
https://mail-archives.apache.org/mod_mbox/lucene-solr-user/201111.mbox/%3ccaf9zkbpho0y-pvskm4dkanc7aargacfsshnqbl+noot1ahx...@mail.gmail.com%3E
Based on stacktraces from threaddumps the "useFilterForSortedQuery" was
determined to be a contributing factor, and disabling it improved performance
(exact comparison not provided).
Would be nice to get some more details and a reproducible comparison (SOLR-2646
where are you???) and evluate why useFilterForSortedQuery would be slower in
3.5 then in 1.4 with the same data.
Should consider actively removing the useFilterForSortedQuery=true option if
there are no longer any usecases where it's better then
useFilterForSortedQuery=false
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
