Re:The bugfix that could make the Internet 5% faster
by SquareWheel on Thursday January 12, 2012 @12:38PM
(#3457181)
I never understood that, why would moving assets to another domain name speed things up? Wouldn't it involve another DNS lookup, thus adding to download time?
edit: I remember reading about this on Yahoo's speed guide, actually: http://developer.yahoo.com/performance/rules.html#cookie_fre...
Still don't quite get it though. Cookie data is always passed in HTTP requests for some reason?
Re:The bugfix that could make the Internet 5% faster
by jmileham on Thursday January 12, 2012 @12:42PM
(#3457204)
Yeah, there's an initial hit, but only one DNS lookup per session-or-so if you've got your TTLs right. You're likely to hit hundreds (if not thousands) of assets in a typical Facebook session, though.
Edit: Actually, in Facebook's case, Akamai has a 20 second TTL. But it's not difficult to perform ~1k asset requests in that amount of time... just scroll through a large friend list.
5% fewer bytes in the request headers would seem to be well within the noise in terms of user experience when you consider latency and application runtime.
This is probably a good argument for using a secondary hostname for assets (like facebook, with fbcdn.net), though, if you want to shave the last few bytes off of requests you don't need to track.