httpwatch does some anecdotal testing to conclude that Firefox’s new algorithm for selecting which idle connection to reuse has some strong benefits.
This is great stuff, and in general it should definitely help. This is part of why getting to one-connection-per-domain is an important goal. HTTP’s use of 6 or more connections per domain make it so that each connection must “warm up†independently. A similar algorithm should land in Chrome soon too.
Fortunately, there is a protocol for this stuff too 🙂 Hopefully firefox will pick that up soon too.
Pingback:Some Ways To Make Your Browser Faster Go Unnoticed | ConceivablyTech