You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Speedscope provides a view that visualizes stack traces in chronological order https://github.com/jlfwong/speedscope#time-order . It looks like a flamegraph samples are not aggregated but rather visualized in chronological order. This usually only allows to see long running functions but provides a good chronological overview over the application which can be useful for filtering
Describe the solution you'd like
It would be nice to select alternative visualizations of the flamegraph and see the callstacks in chronological order.
Describe alternatives you've considered
I can import the perf.data into speedscope
Additional context
n/a
The text was updated successfully, but these errors were encountered:
the term for this kind of view is called 'flame chart'
I agree it would be useful to have in addition, but we need to take performance into account as doing this naively can easily be really slow.
note that for now you'll get highlighting during mouse over for events in the timeline and in the flamegraph, which is somewhat close to a flame chart then
Is your feature request related to a problem? Please describe.
Speedscope provides a view that visualizes stack traces in chronological order https://github.com/jlfwong/speedscope#time-order . It looks like a flamegraph samples are not aggregated but rather visualized in chronological order. This usually only allows to see long running functions but provides a good chronological overview over the application which can be useful for filtering
Describe the solution you'd like
It would be nice to select alternative visualizations of the flamegraph and see the callstacks in chronological order.
Describe alternatives you've considered
I can import the perf.data into speedscope
Additional context
n/a
The text was updated successfully, but these errors were encountered: