Google's HTTP/2 codec slows Envoy

42 pointsposted 21 hours ago
by dilyevsky
(apoxy.dev)

11 Comments

basilikum

18 hours ago

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

dilyevsky

18 hours ago

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

adolph

18 hours ago

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.

rightbondsadmin

18 hours ago

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

dilyevsky

18 hours ago

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.

nosefrog

18 hours ago

So tired of these AI generated articles.

dilyevsky

17 hours ago

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

basilikum

9 hours ago

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.

Recommended reading:

https://paulgraham.com/writes.html

Writing is thinking.

In the end you do you, but personally I generally only bother to read things that someone else bothered to write; and so far that has heen an extremely good heuristic to distinguish what might be worth reading.

dilyevsky

8 hours ago

That was exactly my process on this article and the rest. Often i actually scrap claude/chatgpt edit because it sounds so fake and rewrite it myself. And like i said elsewhere - diagrams are pure ai because i don’t personally care for react especially for throwaway code. But hey thanks for patronizing tone, as a former googler myself i wouldnt expect less

alt227

17 hours ago

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