An update on Visual Studio performance
I wanted to take the time to thank everyone who has contributed to our UserVoice performance site by entering areas you would like to see us improve and for voting on those items. To date we have had over 4700 posts and votes showing the passion you all have for Visual Studio and its performance. For those that have downloaded the Visual Studio 11 Developer Preview from the Microsoft \Build Conference I would like to encourage you to post any performance issues you are seeing with that drop of Visual Studio as well.
As I said in the initial post Visual Studio’s performance continues to be a hot topic and we appreciate the feedback we have received on this site, and through other forums. We are listening to your feedback and continuing to invest in improving performance across a number of areas you all have posted and voted for on this site along with data we are receiving through the instrumentation provided by PerfWatson described below. I wanted to reiterate that our approach to gathering the key areas to improve are twofold and include:
- Collecting feedback from you to prioritize our work
- Implementing instrumentation in Visual Studio to collect data in cases where the product performs poorly
Collecting Customer Feedback
Please continue to use our single stop for feedback on Visual Studio Performance at our UserVoice site and post items or vote on the performance issues you find are impacting you the most. This feedback has been, and will continue to be, incorporated into our plans as we prioritize our work.
I want to spend a bit more time encouraging you to make use of Visual Studio PerfWatson, which is included in Visual Studio 11 Developer Preview. PerfWatson, much like regular Watson, enables us to collect data from your machine right when you experience a performance problem. This data allows us to pinpoint right when you experienced a significant pause or delay in the product and we can then debug the exact stack that is causing your Visual Studio instance to experience a performance delay. This blog post describes how we are using the data to identify and fix performance problems. By combining your feedback with this data we continue to work on addressing those issues affecting you the most.
What to look for Next
As we finish our performance work and validate the wins I will be posting some videos of before and after scenarios for you to see. Please look for these posts as we enter the new year. I continue to read the posts, comments, vote totals at the UserVoice site along with PerfWatson reports indicating stacks that are being the most problematic. This dual view of human perception along with instrumented data is invaluable to our understanding of what is impacting you the most, and again I appreciate your passion for helping us make Visual Studio better for you.
Thank you for your support,
Larry Sullivan Director of Engineering