Well stated. From my own experience, Asynchronous DNS caused everything to actually load slower. I have no idea why, maybe it's because we are on a shared network or something.
Re:Greatly increase Chrome performance
by pepijndevos on Tuesday May 29, 2012 @05:59AM
(#4036728)
I came across several "woo, pipelining, speed!!!" articles before, but it seems that Opera already has it on by default, and Chrome will too, in a future release: http://en.wikipedia.org/wiki/HTTP_pipelining#Implementation_...
Whimsically flipping flags leads to random inexplicable browser misbehavior a week from now after you've forgotten you changed something.
The reason these flags are off by default is because they have consequences: e.g. pipelining causes random HTTP timeouts if any proxy between you and your destination doesn't understand it. The GPU stuff will all be on by default once it works reliably.
Turn these sorts of experiments on temporarily to see if they affect a page you're working on, sure, but don't think that you're making your browser better by leaving them on.