Closed
Bug 1283054
Opened 9 years ago
Closed 4 years ago
Measure impact of e10s-multi on service-worker-backed navigation
Categories
(Core :: DOM: Service Workers, defect, P3)
Core
DOM: Service Workers
Tracking
()
RESOLVED
INCOMPLETE
| Tracking | Status | |
|---|---|---|
| e10s | - | --- |
People
(Reporter: annevk, Unassigned)
References
(Depends on 1 open bug)
Details
From
https://github.com/slightlyoff/ServiceWorker/issues/920
it seems allocating a new content process and routing the navigation request through there can be expensive for Chrome. If that is the case for our setup as well, that would be problematic.
|
||
Comment 1•9 years ago
|
||
We have to implement our new service worker e10s changes first. What we have now won't work correctly for multi-e10s.
Depends on: ServiceWorkers-e10s
|
||
Updated•9 years ago
|
Priority: -- → P3
|
||
Updated•9 years ago
|
tracking-e10s:
--- → -
|
Assignee | |
Updated•6 years ago
|
Component: DOM → DOM: Core & HTML
|
||
Comment 2•4 years ago
|
||
Presumably this sort of thing has been rolled up into whatever service worker performance work has happened in the last 5 years.
Status: NEW → RESOLVED
Closed: 4 years ago
Component: DOM: Core & HTML → DOM: Service Workers
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•