Task #7463
Bug #7462: integration tests are getting frequent read timeouts
configure the HttpClient to allow more parallel connections
Start date:
2015-11-02
Due date:
% Done:
100%
Milestone:
None
Product Version:
*
Story Points:
Sprint:
Description
The PoolingConnectionManager defaults to 2 connections per route (server) and 20 total, and this is considered too restrictive by today's standards. (2 per server was in the rfc2616 spec, but was later dropped). Up the default to be congruent with current browsers.
Associated revisions
History
#1 Updated by Rob Nahf about 9 years ago
modified HttpUtils, which creates the HttpClients for libclient. Not sure if we need to allow even further customization. An explanation on the optimal number has to do with network congestion if more connections are allowed per server. That's to say, it is unlikely that the number of connection per server will increase over time.
#2 Updated by Rob Nahf about 9 years ago
- Status changed from In Progress to Testing
- % Done changed from 30 to 50
#3 Updated by Rob Nahf almost 9 years ago
- Status changed from Testing to Closed
- % Done changed from 50 to 100
- translation missing: en.field_remaining_hours set to 0.0
deployed to staging and production without incident.
