Posted By: The Channel 9 Team | Mar 7th, 2005 @ 12:02 PM | 40,971 Views | 13 Comments
I found Ian, a Developer on our Performance tools, because of his blog. He has been writing a great series of posts that preview the Performance Profiling tools you'll find in Beta 2 of VSTS.  Pictures are great, but I asked him if he'd also like to do a demo. 

Part 1 comes in at about 13 minutes contains a demo using the performance tools on sample code he downloaded that day from Gotdotnet.  You'll find that it was easy for him to discover an existing performance bug in the code using our tools! 
Enjoy,
josh

http://channel9.msdn.com/devdiv
Media Downloads:
Rating:
0
0
littleguru
littleguru
<3 Seattle
I want Whidbey BETA 2! Really cool video.
dmarsh
dmarsh
Knee draggin'
Awesome demo. Very well executed and explained. Looking forward to this feature.
ZippyV
ZippyV
Fired Up
Does it work on managed and unmanaged languages?
Hey ZippyV,

   All of the features shown in the demo work on both unmanaged and managed, with one exception. That exception is the object allocation and lifetime views, those are for managed code only.

Ian
Yes, it does. Native, managed, mixed - it is all covered.
I'd say this is just about essential for all of us who often take no heed to the large amount of objects we create (often needlessly) and save a lot of memory and CPU cycles in the long run. 

This tool, with a few other minor tweaks, could really bring .NET apps at or above the level of unmanaged apps with relative ease.  I'm glad you included the Gen0,1,2 profiling as well.

Dan
ZippyV
ZippyV
Fired Up
Sweet, thanks guys.
Next time, can you use my code as a bad example (seriously) ? You can find it here on Channel 9.
Is there a good way we can profile a library while running unit tests against it with Unit Test Framework with the UI test runner?

I got the following to work with the command line test runner, but I am not sure if there is a better way:

- Add the specific dll you want to instrument from the UnitTestProjectFolder/bin/Debug
- Add the MSTest.exe path in the 'Executable to launch:' setting.
- Add the parameters to run the tests in your assembly via MSTest

Thanks,
Reid

Microsoft Communities