What is the performance of Visual Studio 2010 compared to 2008?

Question

Thinking about installing Visual Studio on my Asus eee 1000HE. Since this is not a very powerful car, I wonder if I should install 2008 or the new 2010. It looks like a lot of changes have been made to the user interface, etc. Does this mean that now it works more smoothly? Or is it really harder to work?

Answer 1

Given that VS2010 is currently only available as a CTP release, I would install VS2008.

As soon as VS2010 is fully released, without debugging information and optimizations enabled, ask this question and think about its use. For now, if you have 2008, use it. I doubt that 2010 will be faster on your "slow" hardware.

Answer 2

2010, in my opinion, is much slower on older machines. I am currently running it on a Dell 700m with 512 MB of RAM, and although it works, it looks slower and significantly slower than Visual Studio 2008. (Remember that this is a beta version, although I’m sure that the performance settings will be available)

Answer 3

It's a little harder to judge performance differences since you Run it in a virtual machine at this time (there is no separate beta version yet).

Change If I am mistaken in the inability to run it outside the virtual machine, I apologize and correct myself.

Answer 4

Does this mean that now it works more smoothly? Or is it really harder to work?

This is an old post, I know, but I just had to call back and laugh: lol

I had a pretty decent overclocked Wolfdale car built for gaming. Fast enough for just about everything I need to do on my computer, besides editing text files in Visual Studio 2010. Just scrolling up and down in a C # file maximized one of my cores. No jokes.

So, I upgraded to the new 32nm Sandy Bridge processors (3.3 GHz, unlocked model) on the enthusiast motherboard, with 8 GB of Corsair RAM, and scrolling cursor movement in the text buffer in VS2010 uses 30% of the processor (this is correct, using multiple cores). This does not disable plugins and disable display.

Vim in the same file, doing almost everything I can think of, shows 0% CPU usage, always.

The performance of the VS2010 editor is absolutely shameful. There is no other word for this.