Google Networking Best Practices for Large Deployments - Manual (Page 18)

18 Networking Best Practices for Large Deployments
• Chrome on Windows 7
Connections when entering URI: 1
Connections during initial load: 3
Connections during login: 6
Connections after a few minutes idle: 4
Connections when opening Calendar and Docs: 4
Connections when loading a document: 6
Average load: 3.6 connections
Peak load: 6 connections
Idle load: 3.1 connections
• Firefox on Windows 7
Connections when entering URI: 1
Connections during initial load: 4
Connections during login: 9
Connections after a few minutes idle: 3
Connections when opening Calendar and Docs: 11
Connections when loading a document: 17
Average load: 4.1 connections
Peak load: 17 connections
Idle load: 3.8 connections
Based on this, the expected load is:
• Average: (5000 x 3.6) + (3000 x 4.1) = 30,300 connections.
• Peak: (5000 x 6) + (3000 x 17) = 81,000 connections.
• Idle: (5000 x 3.1) + (3000 x 3.8) = 26,900 connections.
Based on this estimate, the proxy environment needs to be able to support at least 30,000
connections, possibly more to avoid problems during peak periods, or if growth is expected. If
the current proxy server environment is running at 50% capacity with 20,000 connections, this
is a sign that it will be necessary to deploy significantly more proxy servers, or to route Google
Apps traffic so that it bypasses the proxy server.