Closed
Bug 1661114
Opened 5 years ago
Closed 5 months ago
Add a setIndex field to the marker table
Categories
(Core :: Gecko Profiler, task, P3)
Core
Gecko Profiler
Tracking
()
RESOLVED
DUPLICATE
of bug 1919845
People
(Reporter: gregtatum, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [fxp])
Bug 1580843 describes adding a tracing index, but instead of doing this, we are planning on doing a set index instead. This index will be used to correlate a larger range of markers into a single set, that the front-end can then correlate together. For instance all the different phases of a Network request, and it can still use the phased marker ideas. The markers will still used all of the phased timing ideas, with start/end markers or duration markers. However, they will then be able to be grouped into a single area.
Severity: normal → N/A
|
Reporter | |
Comment 1•5 years ago
|
||
The front-end piece of this is: https://github.com/firefox-devtools/profiler/issues/2763
Going to backlog.
Priority: P2 → P3
|
||
Updated•2 years ago
|
|
||
Comment 3•5 months ago
|
||
The "set index" will be called "flow ID" in bug 1919845.
You need to log in
before you can comment on or make changes to this bug.
Description
•