Closed
Bug 1738765
Opened 3 years ago
Closed 3 years ago
Isolate (some) ServiceWorkers in separate processes for performance
Categories
(Core :: DOM: Content Processes, enhancement, P2)
Core
DOM: Content Processes
Tracking
()
RESOLVED
FIXED
96 Branch
Tracking | Status | |
---|---|---|
firefox96 | --- | fixed |
People
(Reporter: jesup, Assigned: jesup)
References
Details
Attachments
(1 file)
Creating and especially doing serviceworker operations can be badly affected by content-process MainThread jank -- since operations bounce from a launcher thread to mainthread and then to the worker thread, running events (especially JS) on MainThread can delay the operation for 100's or 1000's of ms.
Moving time-critical ServiceWorkers to isolated processes can solve this problem, at the cost of a processes-worth of memory (and some time at creation time to specialize the process from the prealloc cache).
In order to experiment with this feature, initially we'll use an allow-list of domains; in the future this will be replaced with heuristics to decide when this is needed (fetch handlers, etc)
Assignee | ||
Comment 1•3 years ago
|
||
Updated•3 years ago
|
Severity: -- → S2
Priority: -- → P2
Pushed by rjesup@wgate.com: https://hg.mozilla.org/integration/autoland/rev/8ec82114de67 Process-isolate ServiceWorkers if they match an allow-list of sites r=nika,fluent-reviewers,flod
Comment 3•3 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 3 years ago
status-firefox96:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 96 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•