{"id":5741,"date":"2010-01-24T08:25:54","date_gmt":"2010-01-24T08:25:54","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/bharry\/2010\/01\/24\/state-of-vs-2010-performance\/"},"modified":"2018-08-14T00:20:42","modified_gmt":"2018-08-14T00:20:42","slug":"state-of-vs-2010-performance","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/bharry\/state-of-vs-2010-performance\/","title":{"rendered":"State of VS 2010 Performance"},"content":{"rendered":"

Up until Christmas, I was blogging almost every day about the progress we\u2019ve made on addressing the Beta 2 feedback that VS 2010 had significant performance issues.  Since then, our efforts have hardly taken a break.  I saw active investigations all the way up to Christmas eve and then a bit of a lull until Jan 4th when activity resumed in full force.<\/p>\n

The improvements are so many and so dramatic that I really couldn\u2019t enumerate them all here.  I think the best way to summarize it is to talk about the feedback we are getting from people as they use new builds.  Since our renewed performance effort started, we have produced 3 Super Limited Community Technology Preview releases (SLCTPs \u2013 yeah, a mouth full :)).  These have been delivered to virtually anyone who has expressed performance dissatisfaction, and for whom we could find contact information.  With each one we contact as many recipients as we can and solicit feedback on the changes.<\/p>\n

About a week ago, we delivered SLCTP3.  A few hundred people (outside Microsoft) have received it and so far we have close to a hundred survey responses from them.  We also made a huge push to get everyone in Developer Division upgraded to a January build.  I think, as of late this week, we managed to get over 80% of the division upgraded.  Lastly, we\u2019ve reached out to partner teams like Blend, Exchange, CodePlex and Oslo to upgrade and give us feedback on the new builds.  The difference between now and Beta 2 is staggering.<\/p>\n

Before I go into the details, let me remind you of the results we got from our initial Beta 2 surveys.<\/p>\n

Our initial external customer survey said that approximately 30% of Beta 2 testers where somewhat or very dissatisfied with Beta 2 performance (the earler version of the \u201cPerformance\u201d chart below).  After seeing that and running an internal survey of dogfooders, we found that about 70% of internal users were somewhat or very dissatisfied with Beta 2 performance.<\/p>\n

Now, at SLCTP3, it looks very different.  Our external LCTP3 results look like this.  And remember, all of these results are from people who complained about Beta 2 performance (not the 70% of people who didn\u2019t).  We didn\u2019t give any of the LCTPs to or survey people who were already happy.<\/p>\n

\"clip_image002\"<\/a>\"clip_image002[9]\"<\/a><\/p>\n

\"clip_image002[11]\"<\/a>\"clip_image002[13]\"<\/a><\/p>\n

\"clip_image002[7]\"<\/a><\/p>\n

And our internal dogfooder survey looks like this.  The \u201cimproved\u201d questions are relative to Beta 2.  The Ready To Ship and Feature Satisfaction questions are absolute.  The performance feature satisfaction question was 70% somewhat or very dissatisfied after Beta 2. <\/p>\n

\"image\"<\/a> <\/p>\n

As you can see, the picture looks totally different.  The very dissatisfied numbers are nearly gone and the total dissatisfied are way better.  I have no illusion that we can make everyone happy \u2013 we could work on it for 2 more years and still have a few people who would like even more but I feel like we have really turned the corner.  We aren\u2019t done but we are now ready to go out with a broad Release Candidate and solicit feedback from thousands rather than hundreds.<\/p>\n

Beyond the statistics, some of the verbatim customer comments tell an even more compelling story\u2026<\/p>\n