Comment Feed for Channel 9 - Visual Studio Toolbox: Reporting Performance Issues with PerfWatson http://ak.channel9.msdn.com/ch9/8843/0d9b22ab-5730-4687-8933-9f0c01638843/VSToolbox05_100_ch9.jpg Channel 9 - Visual Studio Toolbox: Reporting Performance Issues with PerfWatson 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. en Wed, 19 Jun 2013 22:13:28 GMT Wed, 19 Jun 2013 22:13:28 GMT Rev9 Re: Visual Studio Toolbox: Reporting Performance Issues with PerfWatson 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.

posted by Alexey_Oyun

]]> http://channel9.msdn.com/Shows/Visual-Studio-Toolbox/Visual-Studio-Toolbox-Reporting-Performance-Issues-with-PerfWatson#c634450132040000000 Thu, 30 Jun 2011 06:46:44 GMT http://channel9.msdn.com/Shows/Visual-Studio-Toolbox/Visual-Studio-Toolbox-Reporting-Performance-Issues-with-PerfWatson#c634450132040000000 Alexey_Oyun Re: Visual Studio Toolbox: Reporting Performance Issues with PerfWatson not related to >2s hangs, but wrt performance, can you guys take a look at the following debugger windows:
  • callstack
  • locals
  • watch
having any one of these open when stopped at a breakpoint brings the IDE to a crawl (see the visible lag when resizing the IDE.)
interestingly enough, the autos window doesn't exhibit this behavior.

posted by piersh

]]> http://channel9.msdn.com/Shows/Visual-Studio-Toolbox/Visual-Studio-Toolbox-Reporting-Performance-Issues-with-PerfWatson#c634450546780000000 Thu, 30 Jun 2011 18:17:58 GMT http://channel9.msdn.com/Shows/Visual-Studio-Toolbox/Visual-Studio-Toolbox-Reporting-Performance-Issues-with-PerfWatson#c634450546780000000 piersh Re: Visual Studio Toolbox: Reporting Performance Issues with PerfWatson 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 !

posted by Sitsch

]]> http://channel9.msdn.com/Shows/Visual-Studio-Toolbox/Visual-Studio-Toolbox-Reporting-Performance-Issues-with-PerfWatson#c634450644610000000 Thu, 30 Jun 2011 21:01:01 GMT http://channel9.msdn.com/Shows/Visual-Studio-Toolbox/Visual-Studio-Toolbox-Reporting-Performance-Issues-with-PerfWatson#c634450644610000000 Sitsch Re: Visual Studio Toolbox: Reporting Performance Issues with PerfWatson posted by Cameron McColl

]]> http://channel9.msdn.com/Shows/Visual-Studio-Toolbox/Visual-Studio-Toolbox-Reporting-Performance-Issues-with-PerfWatson#c634450719160000000 Thu, 30 Jun 2011 23:05:16 GMT http://channel9.msdn.com/Shows/Visual-Studio-Toolbox/Visual-Studio-Toolbox-Reporting-Performance-Issues-with-PerfWatson#c634450719160000000 Cameron McColl Re: Visual Studio Toolbox: Reporting Performance Issues with PerfWatson You can't improve what you don't measure! Keep up the great work!

posted by gbrayut

]]> http://channel9.msdn.com/Shows/Visual-Studio-Toolbox/Visual-Studio-Toolbox-Reporting-Performance-Issues-with-PerfWatson#c634451385940000000 Fri, 01 Jul 2011 17:36:34 GMT http://channel9.msdn.com/Shows/Visual-Studio-Toolbox/Visual-Studio-Toolbox-Reporting-Performance-Issues-with-PerfWatson#c634451385940000000 gbrayut Re: Visual Studio Toolbox: Reporting Performance Issues with PerfWatson @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.

posted by Corrector

]]> http://channel9.msdn.com/Shows/Visual-Studio-Toolbox/Visual-Studio-Toolbox-Reporting-Performance-Issues-with-PerfWatson#c634454695840000000 Tue, 05 Jul 2011 13:33:04 GMT http://channel9.msdn.com/Shows/Visual-Studio-Toolbox/Visual-Studio-Toolbox-Reporting-Performance-Issues-with-PerfWatson#c634454695840000000 Corrector Re: Visual Studio Toolbox: Reporting Performance Issues with PerfWatson posted by IDontWantAName

]]> http://channel9.msdn.com/Shows/Visual-Studio-Toolbox/Visual-Studio-Toolbox-Reporting-Performance-Issues-with-PerfWatson#c634456826540000000 Fri, 08 Jul 2011 00:44:14 GMT http://channel9.msdn.com/Shows/Visual-Studio-Toolbox/Visual-Studio-Toolbox-Reporting-Performance-Issues-with-PerfWatson#c634456826540000000 IDontWantAName