Addressing Visual Studio performance

Addressing Visual Studio performance

Rate This
  • Comments 12

Visual Studio’s performance continues to be a hot topic for a lot of customers. We hear you and are investing to improve the performance of the product in those areas that are important to you. There are two key parts to our approach:

  1. Collecting feedback from you to prioritize our work
  2. Using instrumentation in Visual Studio v-next to collect data in cases where the product performs poorly

Collecting Customer Feedback
We are working to make your feedback less ad hoc and give you a single place for feedback on Visual Studio Performance by implementing a UserVoice site specifically focused on performance. Please vote on the performance issues on the UserVoice site. This feedback will be incorporated into our plans as we prioritize our work.

Visual Studio PerfWatson is now a part of Visual Studio v-next. It enables us to collect data from when you experience a performance problem. This blog post describes how we are using the data to identify and fix performance problems. You can help by using PerfWatson with Visual Studio v-next. By combining your feedback with this data we a working to address those issues affecting you the most.

Thank you for your support,

Larry Sullivan
Director of Engineering

Leave a Comment
  • Please add 8 and 8 and type the answer here:
  • Post
  • Overall Visual Studio is not bad, but the part that continues to be an annoyance is that the SQL Server bundled with it never installs cleanly.  Visual Studio is a big investment and people should not have to spend time and money trying to fix a problem Microsoft caused.  Yes, Visual Studio SP 1 fixes the problem, but shouldn't it work after release?

  • Will there be a second service pack for VS2010 addressing any of the issues you've found?

  • sorry if this is off-topic, but is there anything in VS2010 or vNext that will help VS users identify resource (CPU, memory) consumption or blocking the UI thread on a per-extension or per-addin basis?  

    For instance, sometimes for a given developer on my team, VS will 'freeze' for a few seconds, or VS as a process will take lots of memory.  At the moment, we're left doing something akin to a bisection search to find the 'offender' (unfortunately not actual bisection since we don't know there to be a single offender causing the issue), but since there's typically not a specific set of UI actions to consistently reproduce the issue, they end up having to spend a few days on each combination to figure out if that particular combination is 'good' or not.

    We even thought about running VS under CLRProfiler (for memory analysis) or a 'regular' profiler, but the resulting perf and productivity hit (even when lowering the frequency of CPU sampling, for instance) makes it more trouble than it's worth.

    PerfWatson seems like a good first pass at the issue, but it doesn't seem to make the data available to the end user (AFAICT)?

    The IE9 experience for start-up seems to be close, where it can tell me that (for instance) the LastPass add-in is causing my start-up to take a full second longer than it would otherwise, asking me if I want to disable it.  Unfortunately, in the VS case, the start-up time isn't really the issue, it's the ongoing usage, making it a bit more difficult to diagnose so far.


  • +1 to the Perf Per Extension stats!    We have lots of issues with VS2010 that end up being an issue with the latest upgrade of one rogue extension...

  • Created a uservoice item for Perf Stats:

  • As @alimbada asks, will we ever actually see the improvements made as a result of our suggestions? What about performance problems in VS11? Will they get fixed, or will we have to wait for, and then pay for, VS12 in order to see a fix to them?

  • Where can I report bug?

    UserVoice looks like a site for suggestions.

  • @C0: Here =>

  • PerfWatson Monitor makes it easier to monitor VS performance:

  • Before VS 2010 was released, Microsoft hyped it up tremendously.  Please don't plow on to v-next without giving 2010 a SP2.  Please don't get amnesia now and forget the customers who bought 2010.  Don't your customers deserve better?

  • Engineering resources are finite.  Barring data-loss/crash bugs (which would be addressed via QFE/hotfix/rollup), I would think a better use of engineering resources would be VS 11 instead of 2010 SP2.  Keep in mind that 1) VS 2008 didn't have SP2 and 2) most (IIRC) VS users get it via subscription, so serving them well means getting a v.Next sooner rather than later.  Service packs (and the like) are much more limited in their scope than what a new version can do.  

    BTW, VS 2010 deserved the hype. It was (and is) a much better experience than VS 2008, and the direction of VS 11 is quite promising.

  • VS 2010 is to my opinion the most buggy release since VS 2003. SP1 didn't solve half of the problems, it introduced only new bugs. Please release SP2 soon.

Page 1 of 1 (12 items)