Closed stevehalliwell closed 3 months ago
https://docs.google.com/document/d/1CvAClvFfyA5R-PhYUmn5OOQtYMH4h6I0nSsKchNAySU/edit#heading=h.yr4qxyxotyw https://github.com/pacojq/ChromeTracing.NET might be of interest https://aras-p.info/blog/2017/01/23/Chrome-Tracing-as-Profiler-Frontend/ see if Process.TotalProcessorTime is useful
Very straightforward addition, the question becomes do we do the timeline to duration conversion ourselves to get the file size down or just leave it for the tool? Do we want instant events for each bytecode? Do we want options to start and stop tracing? Do we need to clean up our method names?
Emit info for consumption by the Google chrome profiling window?