[
https://issues.apache.org/jira/browse/SOLR-10697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16015732#comment-16015732
]
Shawn Heisey commented on SOLR-10697:
-------------------------------------
Although increasing the value worked well for that client, in situations where
the query rate is super high or the hardware has a very small number of CPU
cores available, increasing the number of requests that can run simultaneously
is probably going to make performance worse, not better. I'm worried that an
increase in the default value will harm more people than it helps.
Empirical evidence one way or the other under different conditions should be
the deciding factor.
> Improve defaults for maxConnectionsPerHost
> ------------------------------------------
>
> Key: SOLR-10697
> URL: https://issues.apache.org/jira/browse/SOLR-10697
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Varun Thacker
> Priority: Minor
>
> Twice recently I've increased
> {{HttpShardHandlerFactory#maxConnectionsPerHost}} at a client and it helped
> improve query latencies a lot.
> Should we increase the default to say 100 ?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
