TechPrufer
Sign inGet started

Blogs›Cloudflare›Go HTTP Client Connection Pooling

Go HTTP Client Connection Pooling

Go HTTP Client Connection Pooling

1
posts
2015

Cloudflare's engineering blog has explored various aspects of Go programming, including performance optimization and debugging. This post details the internal workings of the Go standard library's `net/http` client, specifically focusing on its connection pooling mechanism and the concept of 'late binding' to minimize roundtrip latency. The post illustrates how the client intentionally races between dialing a new connection and retrieving an idle connection from the pool, and how this mechanism is analogous to techniques used in other systems like Chromium and Cloudflare's own Railgun.

2015

What's inside net/http? Late binding in the Go standard library

12/21/2015

This post provides a deep dive into the Go standard library's `net/http` client, explaining its connection pooling strategy with a default size of two idle connections per remote host. It highlights the intentional race condition between dialing a new connection and retrieving an idle one, and introduces the concept of 'late binding' as a technique to reduce roundtrip latency. The author also draws parallels to similar mechanisms in Chromium and Cloudflare's Railgun, emphasizing the importance of robust connection management for performance.