You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Varun Thacker (JIRA)" <ji...@apache.org> on 2018/02/02 17:40:00 UTC
[jira] [Commented] (SOLR-10697) Improve defaults for
maxConnectionsPerHost
[ https://issues.apache.org/jira/browse/SOLR-10697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16350709#comment-16350709 ]
Varun Thacker commented on SOLR-10697:
--------------------------------------
Patch which raises the max connections per host at 10k . All tests pass fine.
I unified the http settings for both the update thread pool and search thread pool into HttpClientUtil . Initially I was hesitant but then I thought they are the same values and probably will remain the same in the future i.e even if Solr creates multiple thread pools ( one for external requests and one for internal ) , these settings will be for the internal thread pool
> 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
> Assignee: Varun Thacker
> Priority: Minor
> Attachments: SOLR-10697.patch
>
>
> 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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org