Increase number of max sockets per group for WebSocket connections.
This change makes ClientSocketPoolManager aware of SocketPoolType so it can
pick a different limit for normal socket pools and WebSocket socket pools.
As an initial (experimental) setting, number of max sockets per group for
WebSocket connections is raised to 30, and other limits are set to the same
value as normal socket pools. This configuration should be revisited later
when WebSocket protocol stack starts to work and a good amount of usage metrics
are collected.
BUG=118268
TEST=none
Review URL: http://codereview.chromium.org/9764003
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@128044 0039d316-1c4b-4281-b951-d872f2087c98
diff --git a/chrome/browser/browser_process_impl.cc b/chrome/browser/browser_process_impl.cc
index 7369e4cf..10d14ed 100644
--- a/chrome/browser/browser_process_impl.cc
+++ b/chrome/browser/browser_process_impl.cc
@@ -715,8 +715,10 @@
net::kDefaultMaxSocketsPerProxyServer);
int max_per_proxy = local_state_->GetInteger(prefs::kMaxConnectionsPerProxy);
net::ClientSocketPoolManager::set_max_sockets_per_proxy_server(
+ net::HttpNetworkSession::NORMAL_SOCKET_POOL,
std::max(std::min(max_per_proxy, 99),
- net::ClientSocketPoolManager::max_sockets_per_group()));
+ net::ClientSocketPoolManager::max_sockets_per_group(
+ net::HttpNetworkSession::NORMAL_SOCKET_POOL)));
// This is observed by ChildProcessSecurityPolicy, which lives in content/
// though, so it can't register itself.
