Closed
Bug 757621
Opened 13 years ago
Closed 13 years ago
Increase max HTTP connection limit on mobile
Categories
(Core :: Networking: HTTP, defect)
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: jduell.mcbugs, Assigned: mcmanus)
Details
Are we still sure 6 is the best limit for total simultaneous HTTP connections on mobile?
android/app/mobile.js:pref("network.http.max-connections", 6);
Would be nice to have a higher limit if/when it's performant--I imagine it'd make a significant difference for many sites.
Is this also the B2G limit, or does that live somewhere else?
I believe Patrick came up with this number, so assigning to him, mainly as a reminder in case this needs to be revisited. Feel free to mark WORKSFORME if you still think this is the right limit, Patrick.
Reporter | ||
Updated•13 years ago
|
Summary: Increase → Increase max HTTP connection limit on mobile
Comment 1•13 years ago
|
||
Some comparisons:
http://www.stevesouders.com/blog/2011/09/21/making-a-mobile-connection/
This post says that Android stock browser uses:
"Android 2.2 has a max of only 4 HTTP connections which limits parallel downloads. (This was increased to 8 in Android 2.3 and 35 in Android 3.1"
Comment 2•13 years ago
|
||
Assignee | ||
Comment 3•13 years ago
|
||
my next step here will be something more subtle than just increasing the parallel connection count. increased parallelism helps cover up latency, which is good - but it also obscures our ability to schedule our most important resources on the bandwdith.. e.g. the js and css are slowed down by the large images sharing the small pipe simultaneously which is very very bad. I think we just learned something from some google spdy data that will help inform that algorithm.
given that, I'm going to wontfix this particular bug.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•