Increasing Google Chrome’s max-connections-per-server limit to more than 6

IE is even worse with 2 connection per domain limit. But I wouldn’t rely on fixing client browsers. Even if you have control over them, browsers like chrome will auto update and a future release might behave differently than you expect. I’d focus on solving the problem within your system design.

Your choices are to:

  1. Load the images in sequence so that only 1 or 2 XHR calls are active at a time (use the success event from the previous image to check if there are more images to download and start the next request).

  2. Use sub-domains like serverA.myphotoserver.com and serverB.myphotoserver.com. Each sub domain will have its own pool for connection limits. This means you could have 2 requests going to 5 different sub-domains if you wanted to. The downfall is that the photos will be cached according to these sub-domains. BTW, these don’t need to be “mirror” domains, you can just make additional DNS pointers to the exact same website/server. This means you don’t have the headache of administrating many servers, just one server with many DNS records.

Leave a Comment