Closed
Bug 1245793
Opened 7 years ago
Closed 3 years ago
investigate responsiveness metric for osx
Categories
(Testing :: Talos, defect, P3)
Testing
Talos
Tracking
(e10s+)
RESOLVED
INACTIVE
Tracking | Status | |
---|---|---|
e10s | + | --- |
People
(Reporter: jmaher, Unassigned)
References
(Blocks 1 open bug)
Details
we are turning on responsiveness metric (chrome only, not content) in bug 710296. This posts ~55 for non-e10s and <10 for e10s. For osx, sometimes we get values like this, but normally for both e10s and non-e10s, we get something in the 70K-80K range. This puts doubt into either the responsiveness collection, or the osx 10.10.5 configuration we are using in automation.
Reporter | ||
Comment 1•7 years ago
|
||
:jimm, can you look into this or find someone to look at it as you have expressed an interest in responsiveness?
Flags: needinfo?(jmathies)
Comment 2•7 years ago
|
||
For reference, the main implementation in Gecko is here: https://dxr.mozilla.org/mozilla-central/source/toolkit/xre/EventTracer.cpp and the Mac-specific bits are here: https://dxr.mozilla.org/mozilla-central/source/widget/cocoa/WidgetTraceEvent.mm https://dxr.mozilla.org/mozilla-central/rev/584870f1cbc5d060a57e147ce249f736956e2b62/widget/cocoa/nsAppShell.mm#106
![]() |
||
Updated•7 years ago
|
tracking-e10s:
--- → ?
Flags: needinfo?(jmathies)
Comment 3•7 years ago
|
||
To be clear, this isn't e10s specific, but we're interested in having this data for measuring e10s
Blocks: e10s-perf
Updated•7 years ago
|
Priority: -- → P3
Updated•3 years ago
|
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → INACTIVE
You need to log in
before you can comment on or make changes to this bug.
Description
•