Performance Profiling | CPU Usage Tool
Vložit
- čas přidán 22. 05. 2024
- A good way to start investigating performance issues in your app is to understand its CPU usage. Profiler PM Esteban Herrera shows how to collect and analyze CPU usage data for your applications.
Learn more about profiling in Visual Studio at aka.ms/vsprofilingdocs/?&WT.m...
Learn more about the CPU Usage tool at docs.microsoft.com/en-us/visu.... - Věda a technologie
This is pure gold. I am currently migrating my Matlab code to C++ and the profiler comes in handy when pinpointing suboptimal code emulating algorithms.
This video is very helpful.Thank you for your video!
Any tips about making the diagession file collected for an azure webapp aware about the correct symbols?
are those tools available for cpp?
Thanks for the great content! :)
Tried setting the symbols path where I have them and have the diagsession file in the same folder with the symbols.i.e the .pdb files with no success
that blue on dark gray is hard to read in the func name list at 13:50.
Great Tool.
Thanks for the video. Unfortunately, this tool is not working at the moment for those with nvidia cards! The bug is unsolved for a long time now.
What does "IO" mean in the profiler? My code does literally 0 disk io but the IO section is still really high.
This ^
is there a way to see the profiling without stopping the app? (live)
Try the Diagnostic Tools window it can help with non-stop profiling. At least in particular.
It's a shame that it doesn't actually work. "There is no data in the current set of filters"
Same thing here - obviously there is a problem which I hope they would address
Useless. It tells me my method took 104ms, but it marks it as [System Code] and it's at the bottom of the call tree. No way to drill down to figure out why it's so slow.
This seems really inadequate at narrowing down. How am I supposed to know when exactly my slowdown was? I know the offending function, I want to profile it. Not some random slice of time.
Works well for me.
so low quality.....it should have been in 4k at least
too bad the audio is so terrible