Issue 85323 in chromium: Configurable connections-per-host

[c***@googlecode.com]

Comment #13 on issue 85323 by ***@gmail.com: Configurable
connections-per-host
http://code.google.com/p/chromium/issues/detail?id=85323

What about online analysis applications? My app can run analysis on large
datasets which will block any traffic to that domain for several minutes.
After spending some time on the server-end of the setup, I discovered that
it is actually caused by Chrome and that Firefox does not have this
problem. Using the IP address instead of the domain name during the
analysis, however, *does* work, confirming that this is caused by a low
per-domain connection limit in Chrome.

[c***@googlecode.com]

Comment #15 on issue 85323 by ***@detroitsci.com: Configurable
connections-per-host
http://code.google.com/p/chromium/issues/detail?id=85323

We need configurable connection limits as part of a testing framework we're
building, based on Chrome. We're trying to emulate other webkit based
browsers using Chrome and being able to correctly set the connection limits
would be very helpful.

As an aside, the whole "we know best" attitude that surfaces whenever more
configuration options are requested is a bit maddening. Can't there be
a "QA Mode" command line switch that enables these options for people who
need them?

[c***@googlecode.com]

Comment #20 on issue 85323 by ***@gmail.com: Configurable
connections-per-host
http://code.google.com/p/chromium/issues/detail?id=85323

We need higher per-host connection limits to support our intranet
application. I found out the hard way that this limit applies across all
tabs and windows accessing the same host. We need to open the application
in many windows for some uses cases, and for performance testing.

I would like to see either a configurable option to set the maximum
connections per-host via the command line, network, extension or
environment variable etc. It doesn't matter how it is configured, so long
as the value isn't hard coded.

Alternatively, I would like to see a configurable option to scope the
connection-limit to each open window. Each instance of the intranet
application running in a different window would have their own set of 6
connections to the server. This could be the best scenario for enabling
automated performance testing.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[c***@googlecode.com]

Comment #21 on issue 85323 by ***@chromium.org: Configurable
connections-per-host
http://code.google.com/p/chromium/issues/detail?id=85323

Whenever web apps require more connections, they do domain sharding. That
has some DNS related costs, but for an intranet app, I see no reason why
that would be costly. Is there a reason you don't just do that?
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[c***@googlecode.com]

Comment #22 on issue 85323 by ***@gmail.com: Configurable
connections-per-host
http://code.google.com/p/chromium/issues/detail?id=85323

It is possible that we will introduce multiple domains to workaround this
issue, however this may cause difficulties when arranging SSL
certificates. Our application will be installed at many locations for many
clients, and arranging the correct wildcard SSL certificates is an
increased overhead I would like to avoid.

But I see no reason why making MaxConnectionsPerHost configurable would be
costly, especially since prior-art exists with MaxConnectionsPerProxy. I
would be happy to work on that and submit a patch, if you would be willing
to commit it.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[c***@googlecode.com]

Comment #23 on issue 85323 by ***@chromium.org: Configurable
connections-per-host
http://code.google.com/p/chromium/issues/detail?id=85323

To my knowledge we don't have a command line flag for max connections per
proxy.

In general, the Chromium project is very against configuration options. I
understand power users sometimes want them. We do not try to make Chromium
perfect for all users. The costs include: complexity in settings UI, code
complexity+increased maintenance, extra bug reports for unsupported
configurations, etc.

In your case, I would suggest using: domain sharding, SPDY, and/or
WebSockets. It's not immediately clear to me why your intranet app requires
so many connections. My inclination is that this problem should be fixable
at the app layer and should not require browser level changes.

I forgot to answer an earlier request of yours: per-window connection
limits. They are fundamentally not achievable given how we structure our
code. In short, the reason is the networking library is not aware of
windows or anything. Longer explanation is too long for this bug report.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[c***@googlecode.com]

Comment #24 on issue 85323 by ***@gmail.com: Configurable
connections-per-host
http://code.google.com/p/chromium/issues/detail?id=85323

My mistake, MaxConnectionsPerProxy is set by policy
(http://www.chromium.org/administrators/policy-list-3#MaxConnectionsPerProxy).

Hopefully others will vote for this issue. I remain convinced that this is
an issue that should be configurable within Chrome, as the connection
limits will cause applications to misbehave once multiple windows to the
same host are opened.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[c***@googlecode.com]

Comment #30 on issue 85323 by felipe.contreras: Configurable
connections-per-host
http://code.google.com/p/chromium/issues/detail?id=85323

As a user, I can't just go to about:config and change
network.http.max-persistent-connections-per-proxy to fix my problems.

And sure, this might not be the correct ticket, but the correct one is
closed as well. Good job in keeping all the tickets as WontFix, that still
doesn't solve the huge problem people have been having for YEARS.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[c***@googlecode.com]

Comment #33 on issue 85323 by ***@gmail.com: Configurable
connections-per-host
http://code.google.com/p/chromium/issues/detail?id=85323

For me, my js files are divided into small files in development evironment,
so I want that when I debugging my code.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[c***@googlecode.com]

Comment #34 on issue 85323 by ***@gmail.com: Configurable
connections-per-host
http://code.google.com/p/chromium/issues/detail?id=85323

Curious, how did folks at EtherPad (which is now at Google?) end up dealing
with this limitation?

With html+javascript webapps making lots of REST api connections, this
seems like a straightforward and important enhancement that really improves
the usability (even possibility) of some applications.

Does anyone know if it's possible to workaround this connection limit in a
chrome web app? I guess so since there are google drive sync tools
(assuming more connections allows faster download of a bunch of small
files).

Does anyone know if using the SPDY (HTTP/2.0?) protocol instead of HTTP/1.1
effectively works around this limit? Sorry, not sure exactly what I mean
here, I'm wondering about its better pipelining.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[c***@googlecode.com]

Comment #35 on issue 85323 by ***@gmail.com: Configurable
connections-per-host
http://code.google.com/p/chromium/issues/detail?id=85323

Yes SPDY definitely gets around the problem. Except if you want it to work
under Apache + Solaris :)
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[c***@googlecode.com]

Comment #36 on issue 85323 by ***@gmail.com: Configurable
connections-per-host
http://code.google.com/p/chromium/issues/detail?id=85323

FYI the RFC2616 limitation of two connections per server has been removed
in the latest HTTP/1.1 RFCs http://tools.ietf.org/html/rfc7230#page-80.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[c***@googlecode.com]

Comment #37 on issue 85323 by ***@makhijani.org: Configurable
connections-per-host
https://code.google.com/p/chromium/issues/detail?id=85323

I keep running out of sockets for hosts on google.com because of multiple
tabs and extensions accessing Google properties that maintain open-sockets.
(i.e. sometimes Gmail breaks due to the Hangouts extension holding too many
sockets, or even Google search will not load). As soon as I "flush sockets"
this is resolved. This limit is very frustrating and for some reason has
only started causing issues recently (on multiple computers, multiple
networks, but OS X). I have tried both the beta and stable Chrome channels.
I found this ticket because I was looking for a way to up the limit -- but
more important I think is the point not being considered, which is that
while the 6-connection limit might be okay for a given tab of a site, it
starts causing problems when each tab on the same domain is holding open
persistent connections.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[c***@googlecode.com]

Comment #39 on issue 85323 by ***@carolinanetworking.com: Configurable
connections-per-host
https://code.google.com/p/chromium/issues/detail?id=85323

Zoneminder, security camera server application, requires multiple streams
and only works with Firefox because of the aforementioned limitation.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[c***@googlecode.com]

Comment #41 on issue 85323 by ***@gmail.com: Configurable
connections-per-host
https://code.google.com/p/chromium/issues/detail?id=85323

I am saddened to see the Chrome developers thinking that they know what
*all* their users needs, and refusing to give them the flexibility they
might require for some particular use cases.

It is perfectly fine that the Chrome developers run test and set a default
value which is fine for most uses.
But why refuse the possibility for the user to change that ?
With that kind of reasoning you make Chrome an average browser... a browser
that works for most people... but it doesn't have the top notch features
some might need.

There is already a lot of setting in the chrome-urls and I can't really
understand why adding that particular one would hurt, if it's a common
request over the years ?
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[c***@googlecode.com]

Comment #44 on issue 85323 by ***@rebel.net.nz: Configurable
connections-per-host
https://code.google.com/p/chromium/issues/detail?id=85323

Can we please have the per-host connection limit at least configurable? Why
do Chrome developers think they know what is best for me?
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[c***@googlecode.com]

Comment #46 on issue 85323 by ***@gmail.com: Configurable
connections-per-host
https://code.google.com/p/chromium/issues/detail?id=85323

Also hurting from this issue.

My company has created our own web browser which uses Chromium. Our
customers will use this browser to surf web applications from my company.

These web applications display a lot of data from various data sources.
Normally, each application need to send 10-30 requests to get data from
data sources.
The 6 connections per host limit is really painful because it blocks a lot
of requests.

I'm really appreciate if Chromium development team can provide an ability
to config or just suggest us how to increase this limit.

I believe people in this thread just want a small increasing (e.g. 10
connections per host).


I've already read the performance test result
athttps://docs.google.com/spreadsheets/d/1LVbLb446kgo7H5kgTunBrQ8Xu2V9saMre0GMOpwHZsk/edit#gid=0
and I think it's worth to increase limit.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[c***@googlecode.com]

Comment #47 on issue 85323 by ***@gmail.com: Configurable
connections-per-host
https://code.google.com/p/chromium/issues/detail?id=85323

Same problem here. We have to show 14 Mjpeg streams in one tab, these
streams comes from one http server that manage 14 webcams, but Chrome
clients only lets show 8 webcams, in Firefox works fine.

Mjpeg streams are a special type of jpg that do a request and keeps
connection open while sending images.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[c***@googlecode.com]

Comment #48 on issue 85323 by ***@gmail.com: Configurable
connections-per-host
https://code.google.com/p/chromium/issues/detail?id=85323

It seems like the Chromium guys do not think we really need more than 6 per
host. We use guacamole a lot, and in guacamole, we connect to one single
single, and tunnel through it to multiple target servers. Just like we can
open 10 putty sessions to do some work, now we want to open 10 tabs in
Chrome to do some work. And because this 10 tabs all connect to the same
Guacamole server, it will hit this limit.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[c***@googlecode.com]

Comment #50 on issue 85323 by ***@gmail.com: Configurable
connections-per-host
https://code.google.com/p/chromium/issues/detail?id=85323

Same problem here with mjpeg. Can't watch more than 6 webcams.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[c***@googlecode.com]

Comment #51 on issue 85323 by ***@gmail.com: Configurable
connections-per-host
https://code.google.com/p/chromium/issues/detail?id=85323

I'm sad to see this chromium developer arrogance, I love chromium, but find
myself going back to firefox, as a developer nowdays we use loaders like
amd, systemjs, etc that requiere a lot of connections, how can this
developer from chromium can let as out? It remainds me of another
annoyance, ctrl-tab MRU!!! I can't believe that with 20 tabs open I have to
remember how many ctrl-tabs or ctrl-shift-tabs I have to do to go back to
some tab, and, same as here there have been no interes in resolve it, that
and firebug keep me going back to firefox, like ton of other debs
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[c***@googlecode.com]

Comment #52 on issue 85323 by ***@gmail.com: Configurable
connections-per-host
https://code.google.com/p/chromium/issues/detail?id=85323

Well, ultimately it is still configurable. The design of chromium is
stupid, but if I ever had a use case for something other than 6 I'd just
patch the source. I build it from source already as it is.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[c***@googlecode.com]

Comment #53 on issue 85323 by ***@gmail.com: Configurable
connections-per-host
https://code.google.com/p/chromium/issues/detail?id=85323

"Well, ultimately it is still configurable" - Not really, there's no
runtime configuration option for it. Modifying the source code isn't viable
for the majority of users, especially Windows users.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[c***@googlecode.com]

Comment #54 on issue 85323 by ***@gmail.com: Configurable
connections-per-host
https://code.google.com/p/chromium/issues/detail?id=85323

I am a end user and was impacted by this issue.

My kids online-only-school has web applications that are failing to load
due to this. Yes, I expect my child to be able to have multiple tabs and
connections open without being hindered...

I had to move my kid to FireFox so that his productivity would no longer be
hindered. I'm watching this ticket for an update that lets me know we can
reconsider chrome as the primary browser used for schooling...

I understand the school could make changes... I also understand/expect to
be told to "just use FireFox".

Thanks.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[c***@googlecode.com]

Updates:
Labels: Restrict-AddIssueComment-EditIssue

Comment #55 on issue 85323 by ***@chromium.org: Configurable
connections-per-host
https://code.google.com/p/chromium/issues/detail?id=85323

(No comment was entered for this change.)
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings