Performance Profiling | Part 2: Choosing the right tool
Vložit
- čas přidán 15. 06. 2024
- There are so many profiling tools in Visual Studio that it can be hard to know when to use each one! In part 2 of our multi-part series on performance profiling with PM Sagar Shetty, we explore the different profiling tools in Visual Studio and when each tool can be used.
Sagar covers:
01:00 Performance Profiler tool
12:35 Diagnostics Hub tool
23:15 Performance Profiler tool vs Diagnostics Hub tool
25:29 Profiling Optimization
32:40 Summary
Previous episode in the profiling series:
Part 1: An Introduction: • Performance Profiling ...
Resources:
-- Learn more about profiling in VS here: aka.ms/vsprofilingdocs
-- Run profiling tools with or without the debugger (docs.microsoft.com/en-us/visu...)
-- Optimize Profiler Settings (docs.microsoft.com/en-us/visu...) - Věda a technologie
Good subject, that most of developpers ignore. But IMHO this video must contain a bunch of comprehensive examples that will show the benefit of profiling.
Show us good examples!
Thanks for these videos, really looking forward to some of the deeper dives!
Enjoying that cause of Leslie sharp questions... and she never interrupt the guest good point.
And that smile again 🙂👌🏼
Pm can be lost in crazy explanations, but she keeps the interview in the path
Sagar was using low res camera to help performance optimize this video.
In the Diagnostic Tools, memory usage tab is there a way to trigger a snapshot from code?
Hello Sagar! I am not able to use .NET Performance Counters Tool in my VS 2022. Could you please suggest me how I can do that?
Great video
hi, i want the possibility to see which part of the code takes the most time and how long it takes to execute for a specific action, for example when i log in, i want to see how long it takes and which is the slowest part in the code for that operation (see precise timing and call counts of function in my code), for example a particular function or operation which takes 2 seconds, and the entire login takes 3 seconds. But when i click on Instrumentation (timeline) it doesnt show data, why?
Leslie, you're so bubbly and engaged, we can tell you really enjoy your job and are good at it, which makes it easier for us to enjoy watching.
I also want to thank you partner who also did a great job delivering this critical, and if I'm to be honest, information we simply didn't know existed!
We will be using these tools a LOT in the future.
This is great! Thumbs up Microsoft team!
Is the code for the test app available publicly?
Hey Richard here is the code for the test app github.com/davidfowl/AspNetCoreDiagnosticScenarios.
Profile tests would also be nice, it's not mentioned here.
Too much of irrelevant speech and talking heads are pretty annoying. Content of first 12 minutes (of 35 total): "We have 6 great tools". That's it. I can't watch it further. You guys probably forgot that is not a corporate meeting. Meanwhile. still no neat and clean VS built-in performance profiler instructions available.
I can't agree more!
Hi guys, "show elapsed" is to my knowledge available on all sku's. docs.microsoft.com/en-us/visualstudio/profiling/perftips?view=vs-2019
If you removed "So now were sorta kinda [this]" and "Now were sorta kinda going to [that]" and "Kinda something " and "Kinda ...something else" you could cut this video down by 50%.
SCRIPT IT FIRST
Skip to 13:10 for anything resembling useful info
There's always a knocker in every comment section.
Its kinda sad that ms doesnt make an actual visual studio for linux and mac and rider dominates there. really sad after 20 years i had to learn a new ide for my workplace
1500 times "you know".
And?
If I need to tune performance, my app is gonna be native C++ anyway, not hosted in some CLR VM, and I'm probably quickly going to want to use some instrumentation that does count wait states, not just times when the CPU is busy.
Sorry, but this kind of hello-world videos serve no purpose. I don't actually learn anything watching it. It's a waste of my time.
Took much of irrelavent talk. Thanks for the session but you could have done way better in terms of examples and how to use the tools to actually improve the performance. Not just showing what the tool does.