[
https://issues.apache.org/jira/browse/SOLR-17665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17926134#comment-17926134
]
David Smiley commented on SOLR-17665:
-------------------------------------
The simplest fix is to change indexSearcherExecutorThreads to -1.
But it'd be nicer to allow query-driven experimentation. SolrIndexSearcher
overrides a {{search}} method before handing off to Lucene; all Solr search
flows through this. This method already creates a new IndexSearcher in some
cases; I could imagine it using another IndexSearcher exclusively created for
multi-threaded search. I also observe that with timeAllowed or other query
limits, multiThreaded isn't going to have its effect.
> Perf regression: overhead of multiThreaded=false should be nothing
> ------------------------------------------------------------------
>
> Key: SOLR-17665
> URL: https://issues.apache.org/jira/browse/SOLR-17665
> Project: Solr
> Issue Type: Bug
> Components: search
> Affects Versions: 9.7
> Reporter: David Smiley
> Priority: Major
>
> SOLR-13350 introduced {{multiThreaded}} query param, defaulting to false,
> thus opt-in. But there is still a serious performance impact; only setting
> {{indexSearcherExecutorThreads}} to -1 in solr.xml mitigates the regression.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
