Closed
Bug 802679
Opened 13 years ago
Closed 8 years ago
give background blocklist and addon checker transactions low network priority
Categories
(Toolkit :: Add-ons Manager, enhancement)
Tracking
()
RESOLVED
INACTIVE
People
(Reporter: mcmanus, Assigned: mcmanus)
Details
Attachments
(1 file)
|
2.39 KB,
patch
|
Unfocused
:
review-
|
Details | Diff | Splinter Review |
I hope to make channel priorities a more useful attribute in necko so I'm cleaning up the priority some resource requests are classified with.
the blocklist and versioncheck-bg processes run in the background but are executed with a default priority.
Neither of these changes will have an immediate impact because current prioritization only happens among resources with the same hostname; this is about better meta data to allow experimentation/measurement with other approaches. Specifically to evaluate the impact of pausing background tasks like this while high priority UI-related activity is being retrieved (stylesheets, js html, etc..)
| Assignee | ||
Comment 1•13 years ago
|
||
Attachment #672375 -
Flags: review?(robert.bugzilla)
Comment 2•13 years ago
|
||
Comment on attachment 672375 [details] [diff] [review]
patch 0
Let's get Blair to review this since he works on this code much more than I do as of late.
Attachment #672375 -
Flags: review?(robert.bugzilla) → review?(bmcbride)
Comment 3•13 years ago
|
||
Comment on attachment 672375 [details] [diff] [review]
patch 0
Review of attachment 672375 [details] [diff] [review]:
-----------------------------------------------------------------
Firstly: Cool :)
::: toolkit/mozapps/extensions/AddonUpdateChecker.jsm
@@ +421,5 @@
> this.request.addEventListener("load", function(event) { self.onLoad() }, false);
> this.request.addEventListener("error", function(event) { self.onError() }, false);
> + var priorityChannel = this.request.channel.QueryInterface(Ci.nsISupportsPriority);
> + if (priorityChannel)
> + priorityChannel.adjustPriority(Ci.nsISupportsPriority.PRIORITY_LOWEST);
This will lower the priority for all add-on update checks - including manual checks, which should stay as normal priority.
To do this only for background update checks, check for UPDATE_WHEN_PERIODIC_UPDATE in aReason here:
https://hg.mozilla.org/mozilla-central/file/b08ec0a01619/toolkit/mozapps/extensions/XPIProvider.jsm#l5311
AddonUpdateChecker.jsm is ignorant when it comes to the flags, so add a boolean param to AddonUpdateChecker.checkForUpdates() and UpdateParser() solely to signify that it's a background check.
Attachment #672375 -
Flags: review?(bmcbride) → review-
| Assignee | ||
Comment 4•13 years ago
|
||
blair, thanks - that's excellent advice.
Comment 5•8 years ago
|
||
Per policy at https://wiki.mozilla.org/Bug_Triage/Projects/Bug_Handling/Bug_Husbandry#Inactive_Bugs. If this bug is not an enhancement request or a bug not present in a supported release of Firefox, then it may be reopened.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INACTIVE
You need to log in
before you can comment on or make changes to this bug.
Description
•