865522 - Figure out optimal HTTP connection limits on B2G

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: General, defect)

Description

[Jason Duell]

Right now in b2g/app/b2g.js we set network.http.max-connections to 20. On desktop that number is 256.  :mcmanus came up with the 20 limit from some testing on android a while ago.  It would probably be useful to simply try to tweak the number a bit higher on B2G phones, load a complex page, and see if it gets us better perf.

Patrick suggests things to watch out for with increasing the max-connection limit on a phone: 1) OOM (more network buffering), 2) slower layout (if we load a lot of things in parallel it may take longer for stuff we need for initial layout to finish loading), or 3) worse responsiveness (clicking link or other nav when page is still loading may run into clogged network buffers).

How do we teak about:config prefs on B2G?  Do we have any metric we're using for page loading time--spinner stopping?  If anyone has suggestions for a pageset to test that'd be handy too.

Comment 1

[Jason Duell]

dougt mentioned that TCP sockets gobble up limited slots on wireless towers, so that's another thing to consider here.  Carriers might not be happy with B2G opening up lots of sockets.

Comment 2

[BMO Automation]

Firefox OS is not being worked on