3 ms·
This brings up an interesting point, who is QUIC/HTTP3 for? Who benefits, who doesn't. I was initially going to ask about why we don't have wider adoption of la
by karmakaze 8y ago
This brings up an interesting point, who is QUIC/HTTP3 for? Who benefits, who doesn't. I was initially going to ask about why we don't have wider adoption of larger packet sizes along with all out increases in bandwidth. If feasible this should be put into the protocol sooner than later.
But on the issue of who it's for, it it helps the less connected be much more connected than it does get hard to argue against it, unless it leads to a loss of decentralization or other prime principle.
- kjeetgill 8y agoI'm no expert, but generally, large packet sizes have all sorts of issues. While they decrease some overhead, they increase the surface for single bit errors, require larger buffers for sending/receiving retransmission buffers, and hurt bad connections while only minimally improving good ones. I don't know the full protocol, but if you can decrease round trips you improve latency while also taking a ton of load off of all intermediate systems, lower RAM used for buffering, etc. "Buffer bloat" has been an issue for a long time.
- karmakaze 8y agoI was just thinking it odd that we're still using the same packet sizes from the 70s despite all the changes in communications technology. Have we just worked around this, or is it actually optimal in some way? As for the pros/cons, I'm only suggesting increasing maximum packet size and using whatever size works for a given connection. I suppose that adds some complexity to negotiation and operating modes. Cost for memory buffers is a good explanation.