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

Question

As far as I know  at the current moment  late 2011 the max-connections-per-server limit remains 6  Please correct me if I am wrong  This is bad that we cannot fix this easily as in Firefox  As far as I know this value is hardcoded   One of the solutions is to download the Chromium s sources and rebuild them  Is there a more easy solution   Is there any tricky way to hack this without creating a dozen of mirror-domains   Why I m asking the question  My task is to create a html-javascript slideshow that will run inside a fullscreened browser  and a huge monitor is hanging on the wall  The javascript is really complicated  it preloads photos and makes a lot of ajax calls to my web services  If WIFI connection is slow  if 6 photos are loading  the AJAX calls fail  the application runs bad  I want a fast solution based  on http or browser or ubuntu tweak something else  because rebuilding the javascript app will take days   Offtopic  do you know any other things that can be tweaked in my concrete situation

User · Answer

I don t know that you can do it in Chrome outside of Windows -- some Googling shows that Chrome  and therefore possibly Chromium  might respond well to a certain registry hack     However  if you re just looking for a simple solution without modifying your code base  have you considered Firefox  In the about config you can search for  network http max  and there are a few values in there that are definitely worth looking at   Also  for a device that will not be moving  i e  it is mounted in a fixed location  you should consider not using Wi-Fi  even a Home-Plug would be a step up as far as latency   stability   dropped connections go

User · Answer

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    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   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

User · Answer

BTW  HTTP 1 1 specification  RFC2616  suggests no more than 2 connections per server      Clients that use persistent connections SHOULD limit the number of simultaneous connections that they maintain to a given server  A single-user client SHOULD NOT maintain more than 2 connections with any server or proxy  A proxy SHOULD use up to 2 N connections to another server or proxy  where N is the number of simultaneously active users  These guidelines are intended to improve HTTP response times and avoid congestion

User · Answer

There doesn t appear to be an external way to hack the behaviour of the executables    You could modify the Chrome ium  executables as this information is obviously compiled in  That approach brings a lot of problems with support and automatic upgrades so you probably want to avoid doing that  You also need to understand how to make the changes to the binaries which is not something most people can pick up in a few days   If you compile your own browser you are creating a support issue for yourself as you are stuck with a specific revision  If you want to get new features and bug fixes you will have to recompile  All of this involves tracking Chrome development for bugs and build breakages - not something that a web developer should have to do   I d follow  BenSwayne s advice for now  but it might be worth thinking about doing some of the work outside of the client  the web browser  and putting it in a background process running on the same or different machines  This process can handle many more connections and you are just responsible for getting the data back from it  Since it is local ish  you ll get results back quickly even with minimal connections

[google-chrome] Increasing Google Chrome's max-connections-per-server limit to more than 6

Examples related to google-chrome