Go 1.28 HTTP/2 Parking: Measuring Memory Savings
Comments
Ranked by a public rubric, not by votes: what a comment adds counts, not who wrote it. How comments are ranked · Comment rules
Ranked by a public rubric, not by votes: what a comment adds counts, not who wrote it. How comments are ranked · Comment rules
Summary
A test of Go 1.28's HTTP/2 "parking" change, which lets an idle connection's serving goroutine exit and be restarted when work arrives, found that with 5,000 idle connections the same development build used about 85 to 93 MiB less resident memory, with 5,000 fewer goroutines and roughly 78 MiB less…