-
Notifications
You must be signed in to change notification settings - Fork 710
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adding a UserCommand to convert etl files to speedscope.json or updating NetperfToSpeedScope #1688
Comments
@EmosewaMC, I recommend that you look at https://docs.microsoft.com/en-us/dotnet/core/diagnostics/dotnet-trace. It is possible to convert from |
The main question which I kind of buried in here is how can I convert an |
Oh, I see. Sorry, I mis-read your question. I am not aware of a way to do this via the command line. It is available through the |
Although not PerfView I have needed this functionality as well and have added it to ETWAnalyzer. I have copied the PerfView code which is very well designed. That was easy. https://github.com/Siemens-Healthineers/ETWAnalyzer It gives you also the option to sum all threads into one to get an overview of the total CPU consumption which I use sometimes to see what is costing too much CPU in total. |
I've noticed that there is a UserCommand called
NetperfToSpeedScope
however giving that method a provided etl file, as it is stated in its comments results in an error due to the etlx file not being found. I am unsure if there is a way to give the UserCommand a .netperf file since as far as I can tell from documentation the .netperf format is deprecated but this would likely cause the program to also look for a .etlx file which may not exist since I cant find where these are generated.My main question is, is it worth the time to put in a PR to add a UserCommand to convert an etl file to SpeedScope, or does the current method work but need some more specific files that I am not looking for?
If NetPerf is not deprecated, how would I obtain this data using PerfView so I can quickly convert traces to the SpeedScope format?
The text was updated successfully, but these errors were encountered: