Speed up Chrome's network stack by enabling HTTP Pipelining. Pipelining issues multiple requests over a single connection without waiting for a response.
Response headers must have the following properties:
Pipelining does not begin until these criteria have been met for an origin (host and port pair). If at any point one of these fail, the origin is black-listed in the client. If an origin has successfully pipelined before, it is remembered and pipelining begins immediately on next use.
Pipelining is available on all platforms in about:flags starting with Chrome 18. It is disabled by default.
1% of canary channel users who've opted in to reporting usage statistics will be used for a field trial. The field trial runs in the background. Once per session it will issue a few test requests to 184.108.40.206 or 220.127.116.11. These servers are owned and operated by Google. They run a simple HTTP pipelining test server. The stats are recorded in Chrome and reported to Google using the existing Chrome histogram system.
In the future, more users will be included in this field trial.