Google's HTTP/2 codec slows Envoy

Engineers investigated a significant CPU performance regression in the Envoy proxy after switching from the nghttp2 codec to Google's oghttp2. The analysis confirms that the new codec is less efficient for header-heavy traffic and provides insights into benchmarking methodologies for network proxies.
A while back we rolled a routine Envoy upgrade to one of our customers' dedicated proxies. Same config, same traffic, and the CPU graphs stepped up by roughly a fifth. This is the kind of chart that earns you a calendar invite with no agenda, so we decided to get ahead of it and started digging in.
Get the full story
Sign up for Headlinne to unlock AI insights, political bias analysis, and your personalized news feed.
Create free accountAlready have an account? Sign in