Add the ability to annotate flows between markers
Categories
(Core :: Gecko Profiler, enhancement)
Tracking
()
Tracking | Status | |
---|---|---|
firefox134 | --- | fixed |
People
(Reporter: jrmuizel, Assigned: jrmuizel)
References
(Blocks 1 open bug)
Details
Attachments
(2 files)
Perfetto (flow_ids) and ETW (activityID)(docs) both have support for this kind of thing.
I believe adding these annotations and exposing them in the UI would be valuable for better understanding what's happening in profiles and help when comparing to Chrome.
Assignee | ||
Comment 1•6 months ago
|
||
Updated•6 months ago
|
Assignee | ||
Comment 2•5 months ago
|
||
Here's an an example profile that has some flows for image decoding: https://share.firefox.dev/3Uky4su
Comment 4•5 months ago
|
||
Since the meaning of a flow ID depends on the marker's timestamp, I worry that we might get into trouble when we use flow IDs with "backdated" markers. We'll need to say something like this somewhere: "When using Flow IDs generated from a pointer, make sure this pointer was valid at the time of the marker timestamp". It may be tricky for the implementation to enforce this.
Comment 5•5 months ago
|
||
I've filed https://github.com/firefox-devtools/profiler/issues/5178 for the front-end part.
Comment 6•5 months ago
|
||
For interval markers, is the flow ID associated with the start timestamp or the end timestamp of the marker? I can think of ways to cause trouble with either choice.
I don't have a suggestion for a solution. Maybe we can pick the start timestamp for now and see how much trouble we run into.
Updated•4 months ago
|
Assignee | ||
Comment 7•4 months ago
|
||
With this applied I can trace through a lot of the runnables and can follow an HTTP request from the child to the parent and then back to the child right up to the HTML parser.
Updated•4 months ago
|
Updated•4 months ago
|
Description
•