Performance profiling has always been an art. I find myself looking down long lists of counters not knowing which ones are relevant and selecting cpu or memory ones because those are obvious. The highlighted hot functions are really useful because it instantly tells you there is a problem. You don't have to hunt for it with a deep knowledge. The next problem is understanding why the performance problem has occurred and that takes great experience and knowledge. It's a really difficult area that in my experience few people are good at. Anything you can do to make it easier would be greatly appreciated
@huraken9483 жыл бұрын
For production environment, is it possible to collect those counters using command line tool and analyze them visually like you did in Visual Studio ?
@romanborysov48214 ай бұрын
Sagar opened the file with the "problematic" method manually. Instead it was expected that he was redirected to that method by clicking flame graph or hot path. "Manual" approach is good for 2-LOC methods, but not 100+ ones. So most interesting demo part (about proper configuring PDB sources) was missing. 🙃
@aaronzhang47173 жыл бұрын
This is next level
@llothar683 жыл бұрын
Why is there no MS love for C++ 😭😭. Can't we get some more and better tooling for C++ too?
@warrenbuckley32673 жыл бұрын
Yeah this would be great. I'd really like a valgrind like tool built into Visual Studio as well.