implement non-interval markers for console.timeStamp console.time, and console.timeEnd
Categories
(Core :: Gecko Profiler, enhancement, P1)
Tracking
()
People
(Reporter: clarkbw, Assigned: canova, Mentored)
References
Details
(Whiteboard: [fp])
Attachments
(2 files)
Updated•8 years ago
|
Updated•5 years ago
|
Updated•5 years ago
|
| Assignee | ||
Updated•1 year ago
|
Updated•1 year ago
|
Updated•8 months ago
|
Updated•8 months ago
|
| Assignee | ||
Updated•6 months ago
|
| Assignee | ||
Comment 3•2 months ago
|
||
Before we switched to the Firefox Profiler in the DevTools, we had
timeline markers for these console methods. But apparently, since we did
the switch, we never added markers for them.
From our conversations with Chrome folks, they mentioned that some JS
frameworks started using these instead of performance.mark/measure
combinations especially the console.timeStamp one since it's just an
instant marker, stating that they are higher overhead. Even though I
don't completely understand their rationale, I think it makes sense to
add markers for these methods. It essentially adds 2 different subtypes
that uses the same ConsoleTimingMarker.
- console.time and console.timeEnd when combined create a duration
marker with a label, similar to performance.mark and measure. - console.timeStamp creates an instant marker with a label.
One edge case is that, console.timeEnd doesn't create any markers when
it doesn't have a console.time with the same title, and vice versa.
Updated•2 months ago
|
| Assignee | ||
Comment 4•2 months ago
|
||
Comment 6•2 months ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/6136cfaf8806
https://hg.mozilla.org/mozilla-central/rev/5ccee7389e73
Updated•2 months ago
|
Updated•1 month ago
|
Updated•1 month ago
|
Updated•1 month ago
|
Updated•1 month ago
|
Updated•1 month ago
|
Description
•