Everything you want to know about Visual Studio ALM and Farming
Brian Harry is a Microsoft Technical Fellow working as the Product Unit Manager for Team Foundation Server. Learn more about Brian.
More videos »
I'm starting to get very mixed messages about people's satisfaction with performance in Beta 2. Clearly performance in Beta 1 was bad. We knew that. We did a lot of work in Beta 2 to make it better and I've heard a lot of people comment on how much better Beta 2 is. At the same time, I'm hearing some people say they are very unhappy about Beta 2 performance. We really need to understand the source of that unhappiness if we are to have any hope of doing anything about it.
We're working on a Beta 2 survey that will go out within the next week and are adding some questions about satisfaction with performance. It will take a week or two to get statistically meaningful data. In the mean time, I'm absolutely interested in pursuing anecdotal stories. If you have good or bad experiences with Beta 2 performance, let me know about them. Tell me what features you were using, what about the performance was good/bad, what kind of system you are running it on, etc. Also, if you don't mind, please give me your contact information so we can follow up with you with additional questions and possibly solutions to try. You can send me email from the email link on my blog page if you are uncomfortable posting contact info publicly. We've set up an internal alias that I can forward all issues to and have someone investigate them.
It's very important to us that we get this right and that our customers be very happy with the release. I'm eager to hear your feedback.
Thank you very much!
Brian
In http://blogs.msdn.com/jaimer/archive/2009/10/23/what-is-new-in-wpf-and-cider-on-the-net-framework-4-and-vs2010-beta-2-release.aspx, Jaime Rodriguez mentions a registry switch that improves the performance of Dev10.
-Mike
After ending a debug session of a simple C# Console app, VSTS locked for 10 seconds+, unfortunately nothing I could reproduce though.
/Gert
I'am working on a WPF Prototyp with VSTS Ultimate 2010 with .Net 4.0 an Vista Sp1 64 Bit. WPF Designer is slow. Also the performance on intellisense is not the best.
When i run VSTS2010 a long time the performance of my machine goes down.
A question the Shift+Alt+F10 on classnames doesn't work anymore? In vs 2008 with this shortkey a can resolve usings.
Thanks for the feedback so far. Keep it coming.
stoffi, ctrl-. does the same thing as Shift+Alt+F10, does that help?
Tim
In native C++:
1) Startup takes a very long time
2) When changing properties it redraws slowly (and in a very odd way.)
3) C++ builds are 3x-5x slower than VS 2003/2005.
4) The Intellisense/squigglys red line indicating errors is sometimes extremely slow in clearing an error.
5) It takes a while for debug sessions to start--actually debugging seems faster than in VS 2008.
6) Creating the intellisense database needs to be seriously optimized.
And while not entirely related, some native C++ executables in 2010 are 20% slower than 2003/2005.
Not related specifically to beta 2, more 2008, but I'm now working with a bunch of former Java developers and I'm constantly hearing them whine about VS performance. There really needs to be a better approach taken to the whole build process.
This is a big impact on developer productivity. VS seems to be getting slower with each successive release and it's at the tipping point for me right now. This needs to be considered a major feature in and of itself.
I kept dealing with "Not Responding" instead of micro-second for each pointer step -- ended up 1 second to 60 seconds during "Not Reponding".
Reloaded-recovery My Vista and only installed Beta 2 and the required programs.
SAME THING. It also does the same thing with WIN7RC machine.
Still have VS2008 on my portable (using that mostly)
Work perfect.
Remembered that I had no problems with any of the VS2008 team and other programs when the machine was XP .... only after I put in VISTA to put in WIN7RC. Still failing on my other machine with WIN7RC.
----- just restarted VS2010 --- failed ---- I think I will check out programs for my imac ......
Hughy
hughy@live.com
What are you doing when you get 1 minute pauses? You seem to be having problems with VS Beta 2 on both Win7 and Vista, is that correct?
I personally think it's great and have switched to it as my main environment (still targeting .NET 3.5 however.) Performance is pretty good on my Gateway P-7811 FX with Windows 7.
Two issues I run into are 1) Windows Forms designer seems to bomb pretty reliably when components in the current project are on a form. 2) WPF designer occasionally locks up when CTL+TABbing between code and designer.
Well I installed Beta 2 last week and have been using it to code some very basic forms in .NET 3.5, although I have come to conclusion leaving VS2010 open a long time must create some sort of memory leak and slowly performance gets ugly FAST. I am running Windows 7 Ultimate with 8GB of memory with 400GB of free space. I have not had the problems listed above, but have noticed an improvement when starting VS2010 up, although I don't know if that is because I upgraded to Windows 7. I have not had VS2010 bomb, although I have not put it through a lot of stress as I did with the first Beta. I will add more when I encounter more bugs.
Wonderful product so far, I've been pleasantly surprised by the breadth of improvements and new features of VS2010. I'm working on a project for Microsoft Consulting Services Public Sector that involves the Social Security Administration, Health Vault, HL7, and NHIN. Because this is a proof of concept, we're able to use VS2010. Here are some of my observations:
* When Microsoft Symbol Server is enabled, starting a debug session takes 5-10x longer than usual, during which time it appears to be loading symbols. Slowly.
* A solution with about 10 projects; it there are build dependency issues. I often have to run a macro to delete bin and obj folders, then rebuild projects in correct order by hand.
* Contracts + PEX doesn't work like it does on VS2008
* After installing and starting to use TFS2010 on the local machine, there are occasional (every hour?) when VS2010 hangs for 2-5 minutes during which a taskbar bubble says VS is busy with "internal operations"
Working with this for 50-60 hours a week, there's more... but this is a good start. Looking forward to feedback. Tks!
The performance is absolutely amazing when compared with VS 2008.
I'm running a Dell XPS 64 bit with 4GB RAM.
After converting the solution to 2010 I timed the opening of the two projects and 2010 was super fast. I think it is due to the project files not being restored which I like very much.
Getting to the different dialog boxes is much snappier than before. The Properties tab, the Options dialog event clicking on Keyboards doesn't take a long time like before.
The code editor itself is really fast.
I'm already using 2010 for some my projects.
tim, thanks for the tip. it works. I hope i remember this new shortkey :-)
The changeset comment policy on tfs doesn't exists anymore?