bharry's WebLog

After ending a debug session of a simple C# Console app, VSTS locked for 10 seconds+, unfortunately nothing I could reproduce though.

/Gert

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.

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

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.

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!

tim, thanks for the tip. it works. I hope i remember this new shortkey :-)

I got really nervous when trying beta 1, because of its poor performance. I was absolutely amazed to see how much faster beta 2 actually is. Playing around I noticed some nice features like the improved startup time of the add reference dialog. However, it does not "feel" that fast as VS 2008, maybe that's the problem.

@Joe

Regarding the following issues:

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.

Thanks for sharing feedback with us. We would like to understand your scenario better and debug the performance issues that you are experiencing. We are working on improving the certain performance aspects of VS2010 but we haven’t seen the issues that you expressed in your comments. It would immensely help us if you could share the solution that you are experiencing this delay on and we can try to reproduce this issue in-house.

You can directly get in touch with me at "amitmo at microsoft dot com" or open a bug through connect with the solution here: https://connect.microsoft.com/VisualStudio/content/content.aspx?ContentID=14631.

A few questions and data points could also help us move forward:

1) Were you running these scenarios over a terminal server session?

2) What is the size of your solution? (#of projects, #of files etc.)

3) What is the configuration of the machine that you were hosting this scenario? (operating system, memory configuration, #of cpu’s, video card etc.)

4) What properties were you trying to modify? Were you trying to modify properties by selecting multiple projects/files?

5) Is your system running in low memory conditions while you are working with Visual Studio?

6) What type of projects do you have in the solution (like ATL projects, projects using STL etc.)?

Thanks,

Amit Mohindra

Windows C++ Team

I'm using an Asus V1s laptop (Intel T7700) with 4G RAM running Windows Server 2008 and Hyper-V.  I'm running VS2010 beta 2 in a Windows 7 pro VM.  I've given the VM 3G of RAM and access to both cores.

I'd say in this configuration that VS2010 beta 2 is sluggish.  I haven't done any side-by-side comparisons but my recollection of the VS2005 RTM in a similar configuration was that it was much snappier.

Folks expecting that WPF would be just as "snappy" or even close to GDI today with 2008 will have to consider that all this new extensibility and managed stuff is a bunch of new code so it's not going to be equally snappy with current hardware.

I haven't had a good look yet at anything of importance so all I can say is the first/cold start perf of simply hovering over the menus at the top (File etc) is sluggish for a moment. And C# Add Class takes it's time to open even if it's already in memory. Unless getting stuff more "snappy" is a priority I wouldn't bother with these though there's more important stuff I bet I just haven't yet have time to find it.

Amit, I have filed some of these issues through connect and have communicated others through other bloggers and/or contacts.

In order to reproduce the issues I outlined:

A) Get a Core 2 Duo E6550 with 3 GB of memory with G31 graphics (i.e. a Dell Vostro)

B) Download an XP VHD from

http://www.microsoft.com/downloads/details.aspx?FamilyId=21EABB90-958F-4B64-B5F1-73D0A413C8EF&displaylang=en

and patch it. For the VMC, use a memory size of 1.3GB. (I think this is too large, but I figured VS 2010 would be a memory hog and checking the working memory set, it is. Still 1.3GB should be more than sufficient if it is the only application running--to be honest, your goal should be to get VS 2010 to have good performance on a Celeron 900 XP with 512MB of memory and lousy Intel graphics. 10 is the new 6.)

C) I had VS 2005 & 2008 already installed, but I doubt this makes a difference except for the hard crash caused by importing [some] existing settings

D) After installing, run VS2010. It takes a relatively long time to load.

D) Create an MFC application.

E) Debug it. You will get a delay when debugging starts. Relative to VC++ 6.0/VS2005/VS2008, it's slow.

F) Changing properties and hitting apply shows a redraw error (a lower level window/tab is erroneously being drawn before the higher level window. Yeah, I've seen this error before.)

G) Full builds are just plain slower. Regular builds are also slower.

As for the two other issues;

1) intellisense: I've seen several non-reproducible bugs with intellisense (in one case it "decided" a function should have started in the middle of a comment and started flagging random things as errors.) The one I'm referring to seems to have to do with picking up changes in included files. What was strange is that if I changed the header to be wrong the error would be flagged almost instantaneously, however when I fixed the header, there was a distinct delay in unflagging the [second] error. In one case, I had to "break" the header a second time to force the change to be recognized.

If I can get a predictable, reproduceable example, i will post it on connect. However, there are definitely bugs in with the intellisense code.

My comment about optimizing the intellisense database is self-obvious. Open a big project and watch it chug away.

I want to point out that it was Microsoft who kept saying "10 is the new 6". VC++ 6 had UI problems and the C++ implementation wasn't very standard, but it was lean and fast.

Every time I start to debug an application or end debugging no matter if it's a console, WPF or Winforms app, VS2010 just reports it's busy with some internal operations and hangs for like 5 to 10 minutes... makes it really hard to do anything with it really.

I've seen reports all over the web, yet the MS admins keep asking for dump files and say they cannot reproduce it. They must be running some pretty awsome machines.

I'm running Windows 7 , on a 4 and an 8 core machine... same problem on both.

I have the same problem: after debugging any type of app, the entire IDE hangs, and clicking on it brings no response at all, it doesn't even focus the window. I've never had the patience of waiting 5-10 minutes for it to start responding, but this happens quite often (about 15 times per day), I use VS for about 6 hours a day. Hanging 2.5 times a day can be pretty annoying.Hope this gets fixed for the release.

Zach, can you please contact me at scarroll -at- microsoft.com?  I'm driving the debugger hangs investigation for the product group.  We are working on root causing TimothyP's issue and I'd like to verify that your instance is something we've already fixed (or fix it if it isn't :) )  Thanks.