Google's HTTP/2 codec slows Envoy | Hacker News Reader

Google's HTTP/2 codec slows Envoy

apoxy.dev

47 pointsdilyevsky10 comments

this looks like it could be an interesting read that i would be bothered to read if a human bothered to write it.

I did write it, the machine did all the react tho (with my help)

I found it worthwhile and interesting. I'm not in deep with proxies every day and have never had to profile performance like this. The writing was very comprehendable to me and the summing conclusions rounded things out nicely. The first conclusion was probably the most practical takeaway: Codec defaults are performance changes. Its obvious in retrospect but also easy to glaze over when reading release notes.

this reminds that protocol compliance and performance aren't always aligned

Im not entirely sure what the motivation was for replacing nghttp2 with oghttp2 - nghttp2 is probably the most used codec for http/2 - so probably not compliance. I think it was mostly about code reuse since oghttp2 is part of QUICHE which is also used in Envoy for QUIC.

So tired of these AI generated articles.

So tired of comments that do nothing other than point out things are ai.

This is a company blog. I run some paragraphs through ai to fix my dogshit sentence structure since english is not my first language (come to think of it, my russian has always been pretty lame too). Get over it

There is absolutely nothing wrong with using AI as a grammar checker and as a help for finding formulations. But I would very much recommend to you to only use it as an aid and to actually write yourself. You can put every iteration through an LLM to flag errors and unclarities. That way you even learn something and the writing is still you thoughts in the end.