4 ms·
> So the main motivation for HTTP/2 is multiplexing, and over the Internet ... it can have a massive impact. > But in the data center, not so much. That's a v
by gwbas1c 2y ago
> So the main motivation for HTTP/2 is multiplexing, and over the Internet ... it can have a massive impact.
> But in the data center, not so much.
That's a very bold claim.
I'd like to see some data that shows little difference with and without HTTP/2 in the datacenter before I believe that claim.
- 0xbadcafebee 2y agoDatacenters don't typically have high latency, low bandwidth, and varying availability issues. If you have a saturated http/1.1 network (or high CPU use) within a DC you can usually just add capacity.
- gwbas1c 2y agoWell, when you assume you make an ass out of u and me! (I get that this probably isn't a high-priority area to study.) > If you have a saturated http/1.1 network (or high CPU use) within a DC you can usually just add capacity. Then I'd be curious how much a lack of HTTP/2 support in the application layer costs. It might be small change for an early stage startup, but when companies get large, these corner cases end up paying peoples' salaries.