Open
Bug 652138
Opened 13 years ago
Updated 2 years ago
we need a max-active connection concept for mobile
Categories
(Core :: Networking: HTTP, defect, P3)
Tracking
()
NEW
People
(Reporter: mcmanus, Unassigned)
Details
(Whiteboard: [necko-backlog])
Mobile has a pretty low set of max-connections (both global and per server). It does this because in a low bandwidth situation over parallelization leads to big queues and lousy interactivity without actually speeding anything up. Mobile should probably have some mechanism that recognizes it isn't always low bandwidth - but that's a different bug. For now, let's acknowledge that low levels of parallel downloads make sense in some situations. Unfortunately our concept of max-total-connections is tied up with max-active-connections. While we want to keep max-active low in these situations we might very well want to keep a larger pool of idle connections (especially to other hosts) around. But right now if we do that we will automatically try and use them concurrently. Doing this could result in a lowering the number of new connections (which are slow) necessary in a low bandwidth situation.
Reporter | ||
Updated•8 years ago
|
Whiteboard: [necko-backlog]
Comment 1•7 years ago
|
||
Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: -- → P1
Comment 2•7 years ago
|
||
Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: P1 → P3
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•