Visual Studio Toolbox: Reporting Performance Issues with PerfWatson
- Posted: Jun 29, 2011 at 11:38 AM
- 63,654 Views
- 7 Comments
Have you ever run into a scenario where a long running task causes the Visual Studio UI thread to hang or become unresponsive? The PerfWatson extension logs these issues and automatically and anonymously reports back to Microsoft.
In this episode, we are joined by Cameron McColl, who explains why the PerfWatson extension was created and how you can install it. He also shows us some collected data and explains how it's used to drive performance improvements and make Visual Studio faster.
Comments Closed
Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation,
please create a new thread in our Forums,
or
Contact Us and let us know.
More episodes in this show
-
Visual Studio Toolbox: Creating and Using Code…
-
Visual Studio Toolbox: Reporting Performance…
-
Visual Studio Toolbox: All-In-One Code Framework
Follow the Discussion
Oops, something didn't work.
What does this mean?
Following an item on Channel 9 allows you to watch for new content and comments that you are interested in. You need to be signed in to Channel 9 to use this feature.What does this mean?
Following an item on Channel 9 allows you to watch for new content and comments that you are interested in and view them all on your notifications page.sign up for email notifications?
Hi,
It is similar to solution provided by Nathan Nesbit blogpost Detecting UI Thread Misuse
And as VS2010 has problems so do our programs, and it would be really nice to have this tool to watch custom wpf applications too.
vs2010 is slow due to WPF crap. It's one of the worst moves microsoft did so far.
vs2008 is really fast in comparison.
Please admit you screwed up already and revert the wpf crap.
How stupidly stubborn can you get ?
It doesn't work so kill it already !
Sitsch: The PerfWatson data refutes your assertion. While there are WPF delays they are not even close to being in the top responsiveness issues we have identified so far.
You can't improve what you don't measure! Keep up the great work!
@Sitsch, WPF isn't the problem, except in making raster fonts no longer eligible which was a horrible move on MS's part. The problem is the new Intellisense. That's what slows everything to a crawl as you actually write code, whether it's C++, C# or XAML for WPF/Silverlight.
The other problem is the new partially C++0x compliant compiler (RAM gobbler edition), which gobbles RAM like there's no tomorrow when templates are involved (e.g., boost variant anyone?). When you run multiple parallel compilers (say eight of them), which these days seems to be a good idea given the standard quad cpu (8 with hyperthreading) hosts people use for development and you better have lots of RAM (where lots >> {i.e., much greater} 4 GB). I am typing this on a host with 12 GB of RAM as we speak, which is about the bare minimum necessary for C++ software development these days.
you should contact the jetbrains. their Resharper causes a lot of Solution open hangs of VS2010
Remove this comment
Remove this thread
close