Closed
Bug 1186580
Opened 9 years ago
Closed 2 years ago
Expose User Timing marks / measures in performance timeline
Categories
(DevTools :: Performance Tools (Profiler/Timeline), defect, P3)
DevTools
Performance Tools (Profiler/Timeline)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: jryans, Unassigned)
References
Details
(Keywords: DevAdvocacy, Whiteboard: [devtools-platform][DevRel:P2])
The User Timing API[1] allows content JS to create custom named marks (single time points) and measures (start / end pairs) for performance measurements.
These should be added as markers in the Perf tool.
[1]: http://www.w3.org/TR/user-timing/
Updated•9 years ago
|
Whiteboard: [devtools-platform]
Comment 1•9 years ago
|
||
May be able to use the PerformanceEntries actor
Comment 2•9 years ago
|
||
This would come in really handy for complex projects in which you depend on a lot of code you haven't written yourself (e.g. node modules), and which also gets called so many times that the performance graph doesn't really help, but if you can set marks in your top level code you at least have some idea of what the app is doing.
Keywords: DevAdvocacy
Updated•9 years ago
|
Whiteboard: [devtools-platform] → [devtools-platform][DevRel:P2]
Comment 4•8 years ago
|
||
This is being tracking in the perf.html project. https://github.com/devtools-html/perf.html/pull/275
Comment 5•7 years ago
|
||
I'm a bit confused about the status here. The PR linked in comment 4 is merged, but I saw people on twitter today complaining about this feature being missing, and I don't obviously see user timing in the timeline....
Flags: needinfo?(gtatum)
Comment 6•7 years ago
|
||
The User Timings work is done in perf-html.io, but not in the DevTools performance panel. The eventual plan is to migrate the Firefox DevTools' performance panel to point to perf-html.io, although I don't anticipate this migration to be done in the next quarter or two. We are currently focused on prioritizing work that will help with Gecko engineer's performance work, and not as much on the web developer-focused features.
See Bug 1418044 for the panel migration work.
Let me know if you'd like to chat more about our current planned work.
Flags: needinfo?(gtatum)
Comment 7•7 years ago
|
||
Greg, thank you for the update! That answers my question.
Depends on: devtools-perfhtml
Updated•6 years ago
|
Product: Firefox → DevTools
Comment 8•2 years ago
|
||
We migrated to the firefox profiler now, where user timing markers are supported. The old performance panel has been removed, so I'm closing this bug now.
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•