Visual Studio 2010 very slow, unusable

I've searched for this topic but can't seem to find posts that relate exactly to what I am experiencing.

I have a Visual Studio solution that I need to work on, its fairly large and contains 16 projects.

Everything is just so so slow and choppy (Except start-up which is actually quite fast).开发者_开发百科

Clicking a line in the text editor, it takes about 5 seconds just to move the cursor.

Switching between files ~1-2 mines (if I'm lucky)

Clicking on 'Tools' ~ 2 minutes for the drop down menu to appear.

If I right click one of the projects then its ~5-10 minutes before I get the drop down menu. During this time my entire PC locks up.

Closing Visual Studio (in rage) ~10-20mins

As for debugging and building.. well I've never managed to get that far.

Looking in task manager (opening this with visual studio going takes a long time) there is nothing running that is consuming a lot of memory/cpu.

I know Microsoft products are not renowned for being fast but this is ridiculous, there is no way I can code anything like this. Something must be wrong.

Any help would be so greatly appreciated, my head is ready to explode.

Visual Studio 2010 Ultimate SP1

Windows 7 x64

Intel i7 950 @ 3.07GHz

6GB RAM (Tri Channel)

2x nVidia GTX 470 (SLI)

My mouse lags over menus too! For menus that are grayed out, it is fine. But for active menus, the mouse feels sticky when moving over them.

One solution i tried and it works is disable rich user experience and disable hardware acceleration.

Tools -> Options -> Environment (General) -> Visual Experience -> uncheck Use hardware graphics accelerator if available.

I have a good graphic card, but stopping visual studio from using graphics hardware makes my mouse sooo smooth now!

Visual Studio is actually quite fast if used properly. For example, I have solution with 45 projects (~600000 loc) that works fine.

It's probably an installed extension that kills the IDE (things like Resharper for example can be memory greedy - disclaimer: I have nothing against Resharper, I use it myself :-).

Here is a link to disable extensions (read also the comments): How to: Disable and Re-enable Visual Studio Tools and Extensions

Thanks for all the replies.

I've switched to using visual c++ express, it's much quicker, now I can actually do some coding.

Best solution I have for now.

Sounds like to much open and very large files to me - then syntax highlighting and IntelliSense can become very complex to calculate. Maybe you also suffer from some Add-Ons.

Does it also happen when you open up VS2010 and create a new project? If not, there might be something wrong with the the solution or project files. Removing the .suo and .sdf files sometimes helps.

Another thing you can try is install VS2010 on another machine to see if it's related to just your machine.

Did you open Resource Monitor in the task manager? It's able to show you disk I/O, it might show you that your virus scanner is accessing everything (happened on my machine).

Hope this helps.

Sebastiaan

Do you have multiple monitors? I experience issues with this if I place the visual studio window on the 2nd screen of my workstation I get mouse lag and other such issues close to what you experience. Although it's close enough to usable for me, but this machine is also running SQL Server which could explain some slowdowns. Make sure that unnecessary services aren't running (like say SQL if you dont need it) and that might help. Also make sure if you are using any extensions that they are the latest (mostly concering memory leak issues with older versions of Resharper).

Try to uninstall Windows Pen Input service (do not simply disable it, otherwise File->Open will stop working in VS, yeah I know...).

Disable intellisense completely (to see if that has anything to do with it). If it helps, start enabling it back until it fails again.

I have been tasked with upgrading to Visual Studio 2010 (Professional) from 2005 in my place of work, and I can say without a shadow of a doubt that I somewhat regret making the switch. The IDE is noticeably - no, significantly slower - than VS 2005. I now wish we switched to VS2008 instead. This is all very worrying because then I'll be seen as the one who made the made the switch and I'll be facing all the negative remarks. I installed SP1 which didn't make much of a difference.

One solution, ~50 projects, 1 MLOC. Windows 7 x64, Intel i7 950 @ 3.07GHz, 4GB of RAM. Pretty well-spec'd machine, I would say.

Windows 7, x64, 12GB memory, very slow right clicks:

The following steps fixed the problem for me. Right click is now instantaneous. Your Mileage may vary:

I deleted the following directory: %AppData%Local\Microsoft\VisualStudio\10.0

and reinstalled these three packages from the Visual Studio 2010 Ultimate DVD

Microsoft SQL Server 2008 R2 Data-Tier Application Framework with this command: \WCU\DAC\DACFramework_enu.msi

Microsoft SQL Server 2008 R2 Data-Tier Application Project: \WCU\DAC\DACProjectSystemSetup_enu.msi

Microsoft SQL Server 2008 R2 Transact-SQL Language Service: \WCU\DAC\TSqlLanguageService_enu.msi

Maybe it's your antivirus. Temporarily disable it and see if VS works better.

I have also experienced very slow performance of Visual Studio 2010. After trying various things, I realised that I had enabled Fuslogvw.exe (Assembly Binding Log Viewer, AKA Fusion Log Viewer). It was writing out assembly binding logs to a directory on my hard drive. This was then being scanned by my Anti-Virus on-access-scanning, which was grinding Visual Studio to a halt.

As soon as I modified the configuration of the on-access-scanning to exclude the directory to which the assembly log was written everything went a lot faster. Disabling the Assembly Binding logging obviously had the same effect.

Details on Fuslogvw.exe here: http://msdn.microsoft.com/en-us/library/e74a18c4.aspx

An answer on stackoverflow relating to anti-virus scanning here: Slowdown of Microsoft Visual Studio due to different Virus scanner

In summary, my answer is to make sure that Fuslogvw.exe is not enabled and/or exclude its log directory from your on-access virus scanner.