Re:Lessons from Building and Scaling Reddit's Ad Serving Pla...
by ErikDub on Monday September 10, 2018 @10:05AM
(#17951869)
The main issue with net/http is that it generates a lot of garbage which is definitely going to show up in your profile if you're handling a lot of requests per second.
Re:Lessons from Building and Scaling Reddit's Ad Serving Pla...
by sagichmal on Monday September 10, 2018 @11:31AM
(#17952508)
Allocation pressure imposed by net/http has never been a top K source of profile CPU burn in any service I’ve ever written, and I’ve written plenty of high-performance, high-QPS services. fasthttp is rarely if ever a good idea.
Furthermore, the HTTP stack doesn't show up on most web servers' profiles. net/http is better understood by the community, interoperates with libraries better (e.g. golang.org/x/oauth2), and is better supported.
Use net/http.