Closed
Bug 1302544
Opened 8 years ago
Closed 6 years ago
Investigate an upper bound on how much performance problem pre-emption could fix
Categories
(Core :: DOM: Core & HTML, defect, P3)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: ehsan.akhgari, Assigned: farre)
References
(Blocks 1 open bug)
Details
We'd like to get a sense of how much time we spend in places in the code where we could benefit from pre-emption. This will require us to look at call stacks where we're running some JS code in a third-party iframe or in a background tab and whether the refresh driver is active in that case (aka whether we'd have liked to paint) or whether there's an unprocessed user input event in the queue (aka whether we'd have liked to process the user input event.)
Once we have this measurement, we can get a sense of an upper bound on how much we could make things better if we were pre-empting the long running task in that case.
Updated•8 years ago
|
Priority: -- → P3
Reporter | ||
Comment 1•8 years ago
|
||
mystor decided to own the data collection stuff here.
Assignee: nobody → michael
Reporter | ||
Updated•8 years ago
|
Assignee: michael → afarre
Assignee | ||
Updated•6 years ago
|
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
Comment 2•6 years ago
|
||
why wontfix? obsoleted by e10s?
Assignee | ||
Comment 3•6 years ago
|
||
Obsolated by bug 1351021.
Updated•6 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•