Ticket #34 (closed defect: fixed)

Opened 2 years ago

Last modified 2 years ago

Updating network.http.max-persistent-connections-per-server causes firefox to stop loading pages

Reported by: planetf1 Assigned to:
Priority: major Milestone: 1.0
Component: Preferences Version: 1.0
Keywords: connections Cc: nigel@cherrybyte.me.uk
Operating System: Windows

Description

Firefox (2.0.0.2) has 2 settings that the extension manipulates network.http.max-persistent-connections-per-server

It sets this to (Max contemporary downloads * Max chunks number per download) + 2

Unfortunately this setting is used by firefox in general usage, and it seems to cause me problems when it gets high - I find that with many tabs open in firefox page loads start to hang/freeze until the setting is reduced to a reasonable number

For general browsing I find having this set to ~4 works fine (with non-persistent connections maxing at ~8 and total connections ~64).

Unfortunately down them all interferes with this.

Have other people seen this? is there a way that downthemall could use it's own quota for #connections?

Change History

2007-02-28 14:06:45 changed by planetf1

Note that just multiplying the two values together isn't necessarily what the user intended.

Often downloads may be from different sites, so as long as the total number of connections (network.http.max-connections is sufficient we're ok)

For example I'd want something like

  • max connections per server : 6 (try to be sociable)
  • max connections for down them all to use per server: 4 (leave some for regular browsing)
  • max simultaneous downloads: 4 (from different sites)

If I was to download 2 files from the same site I'd expect downthemall to use ~50% of it's quota per download

Hope I've explained what I think the intent is, and the problem

Finally note the problem is likely most evident when the max-persistent-connections-per-server is greater than max-connections-per-server

2007-03-13 21:56:41 changed by MaierMan

  • status changed from new to closed.
  • resolution set to fixed.

We rely on these preferences as well, so not overwriting them is not an option.

I checked in some code to abuse those settings less. source:/trunk/chrome/content/dta/manager.js@160#L133

About fine-tuned total/per-server settings in dTa: This suggestion is already tracked elsewhere. ;)

2007-04-09 15:42:33 changed by MaierMan

  • milestone set to 1.0.