Closed
Bug 1341532
Opened 7 years ago
Closed 5 years ago
Measure paint request to display latency
Categories
(Toolkit :: Performance Monitoring, defect)
Toolkit
Performance Monitoring
Tracking
()
RESOLVED
INACTIVE
Performance Impact | low |
People
(Reporter: wcpan, Assigned: wcpan)
References
Details
(Keywords: perf)
In bug 1313465, we want to measure event to dispatch latency, which can be divide to three parts: 1. from user input to event dispatcher (including IPC) 2. from event dispatcher to paint request (mostly in JavaScript engine) 3. from paint request to actual rendering (compositor, gfx ... etc.) This bug measures the third part.
Updated•7 years ago
|
Whiteboard: [qf:p1]
Comment 1•7 years ago
|
||
Harald, please help to triage this bug. As last conversation in Toronto, this is not a blocker, right?
Flags: needinfo?(hkirschner)
Comment 2•7 years ago
|
||
This was marked p1 in triage, but we can reconsider against current needs and put it back in triage.
Flags: needinfo?(hkirschner)
Whiteboard: [qf:p1] → [qf]
Updated•7 years ago
|
Whiteboard: [qf] → [qf:p3]
Comment 3•7 years ago
|
||
People said in triage today that because this doesn't map directly to a release criteria it shouldn't be P1.
Updated•5 years ago
|
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → INACTIVE
Updated•2 years ago
|
Performance Impact: --- → P3
Whiteboard: [qf:p3]
You need to log in
before you can comment on or make changes to this bug.
Description
•