I've got PrefWatson installed, and I unfortunately sometimes have to use about ten running instances of Visual Studio (for ten different solutions). For each instance of devenv, there is a PrefWatson instance. Ten instances of PrefWatson can alone take as much as a quarter of a gigabyte of memory! This seems silly - I'm sure a single process can monitor several instances of devenv, reducing the memory footprint.
I agree with Taz0, there should only be one instance of the perfwatson process that can cover all instances of the devenv application! The memory footprint gets huge when using more than 2-3 instances of devenv!!
I've been PrefWatson for quite some time. It mostly sits silently in the background, but we are told it helps Microsoft improve the performance of Visual Studio. Now that Visual Studio 2012, with its improved performance, is at beta, could you please tell us how the contributions of those using PrefWatson, if any, help achieve performance improvement in VS2012?
I like the idea of this perf watson. I would also like to have a direct benefit of this as a developer using visual studio. I think it would be great if the report give us a clue about what was going on, especially for extensions by giving what visual studio is waiting for (stack trace would be great) and that way it would be possible for us to disable the extension if necessary and report a bug to the developers of that extension.
I saw a message that said that msdev needed flash.ocx for the first time after installing PerfWatson. Was PerfWatson the cause of that error message?
(On my development machine, I try not to add potential problems)