Pull 894 - Difficult to view chromium dotnet traces - Always shows 17 ms and can't visualize user code

[jnuic7]

@adamsitnik
Hey Adam, just attaching the chromium file

trace.chromium.txt

[jnuic7]

@adamsitnik Heres a better one, have a dummy async method GetHello. I looks like it does change times but this time it is 13 ms which the trace should be longer then that
trace.chromium.txt

[adamsitnik]

@jnuic7 could you please provide also the orginial .nettrace file that was converted to chromium

[jnuic7]

@adamsitnik No problem, originally I was just using dotnet trace collect -p 50555 --format chromium but just converted one

trace.chromium.txt
trace.txt

[adamsitnik]

@jnuic7 It looks like a chromium bug. It displays ms instead of s as a time unit.

I took the trace file that you have provided and exported it to chromium and speedscope using latest version of PerfView. The files can be found here: https://gist.github.com/adamsitnik/3f81adfba0ee85145f5c8ebbd8a25d85

After opening with chromium tracing and also web developer tools the time scale shows ms everywhere:

But speedscope shows the correct time:

[jnuic7]

@adamsitnik Great and appreciate the help:) I'll close this out as it seems to be an issue with Chromium. Is there and chance filtering, maybe a dotnet trace param or something is in the works to just see user code?

[adamsitnik]

Great and appreciate the help:)

You welcome!

Is there and chance filtering, maybe a dotnet trace param or something is in the works to just see user code?

dotnet trace, speedscope and chromium don't support it, but PerfView does. Here is a tutorial that explains how to do it with PerfView by using a feature called grouping: https://channel9.msdn.com/Series/PerfView-Tutorial/PerfVIew-Tutorial-4-Grouping-And-Folding

BTW you can add this request to this issue: #1301 as we might create a new tool with more powerful filtering soon