[hobohacker]

We've considered this before, and the performance gains do not appear worthwhile (we've run much more extensive tests than you have on top websites to evaluate potential gains), it has extra complexity, it is more of a Hampering Eyeballs approach rather than a Happy Eyeballs approach, it has potential web compat issues (many sites will not expect you to connect to the IPs other than the first), etc etc.

[IgorPartola]

Sorry, but I can't tell from your profile who "we" is. Are any of your results public? Also, what do you mean by "many websites will not expect you to connect to the IPs other than the first"? My OS's DNS resolver randomizes the A/AAAA records I get on every resolution. The website operator cannot control which IP I will connect to. If you mean that websites don't expect two simultaneous connections, then I would be curious how two different servers would coordinate the fact that each got a TCP connection from the same IP at any scale. How does that interact with NAT? For example I believe some IBM campuses are behind giant NAT's with a single IP address per building or some such. Which websites get confused by this?

[hobohacker]

Sorry, I'm a Chromium dev, and in particular I'm the net maintainer who authored the majority of the current connection management code you are discussing. Our results are not public. The web compat concerns are with more exotic, enterprise configurations, not public ones. They are not the most compelling concerns though.

[IgorPartola]

Cool. +1 for the clarification.