Re:The bugfix that could make the Internet 5% faster
by ajross on Thursday January 12, 2012 @12:16PM
(#3457073)
Packet sizes make very little difference on an unsaturated line, which is often the case on the client side. It's very often not the case on the server side, or on mobile networks. There, it's not at all uncommon to see line saturation at peak usage, and under those circumstances pure bandwidth optimizations can be helpful.
Re:The bugfix that could make the Internet 5% faster
by amalcon on Thursday January 12, 2012 @12:42PM
(#3457206)
The server's uplink is certain to be full-duplex and outbound heavy, so inbound bandwidth is effectively unconstrained. You still could run into line congestion somewhere in the middle, in which case bandwidth optimizations would help, but router congestion is much more common.
Except in mobile networks, as you note.
Re:The bugfix that could make the Internet 5% faster
by jmileham on Thursday January 12, 2012 @12:56PM
(#3457267)
I'd guess that the mean request size is misleading though - it is presumably the average of a mix of lightweight CDN requests and gargantuan app requests loaded up with the egregious cookies jgrahamc mentions. It's not hard to imagine a healthy number of requests hovering right at the brink of breaking into two packets with a 1500 byte MTU.
Re:The bugfix that could make the Internet 5% faster
by dudus on Thursday January 12, 2012 @12:10PM
(#3457044)
I agree that my math is flawed and I ignore the whole TCP package splitting argument. Still that GA cookie could easily be breaking millions of TCP packages every day. But even if the impact is much lower. Why should we keep having such unnecessary data on those HTTP requests?
1. The average size of HTTP request headers is 700 bytes. 2. Of that around 25% is Google Analytics 3. About 50% of web sites use GA
Thus you could save 12% of HTTP request header size across the Internet.
Then he posits that this would make the net 5% faster. How?
If the average size is really 700 bytes then they will fit inside a single TCP packet and so changing it from 700 to 525 will make no difference at all. The entire request will be in a packet. The real cost is multiple packets requiring ACKs and that occurs with the larger header sizes that SPDY specifically targets with HTTP header compression. I've seen many egregious cookies, but the GA ones are tiny.
If you really want to speedup the web you need something like SPDY plus SDCH to do data-aware compression of repeated chunks of HTML.