VS2005 Performance Seriously FUBAR

[clintonG]

I have 11.5 Gb remaining on the master on an XP Pro SP2 machine with 1.5 Gb
RAM. I keep the OS updated. The paging file has been disabled on the master
and relocated to a slave. Task Manager reports 1 Gb of paging file usage. I
defrag with regularity whether need or not. I've trimmed Visual Effects down
to a minimum.

Still -- consistently -- entering the cursor into the source window of the
VS2005 IDE causes VS2005 to light up the disk drive. It takes 10-20 seconds
to wait for the cursor to appear and another 10-20 seconds to highlight text
I want to copy or comment out. This is unique to VS2005 as I have no
problems with any other software.

No word from microsoft.public.vsnet.ide. What could be causing this problem?

<%= Clinton Gallagher
NET csgallagher AT metromilwaukee.com
URL http://clintongallagher.metromilwaukee.com/

 

[Chris Dunaway]

This is just a thought, but back in the VS2002/2003 days, the context
sensitive help in VS would cause a slowdown and the solution was to
just disable the context sensitive help. Don't know if that will help,
but it might be worth a shot.

 

[Rob R. Ainscough]

It's a feature.

I'm not defending VS 2005 IDE, but it does do A LOT - however, I agree it
has some serious hardware requirements to run smoothly -- I found going from
1GB RAM to 2GB RAM and getting WD 10,000 rpm Raptor SATA hard drives helped
improve performance considerably. I use a single processor PC at home, but
at work I have a dual processor PC with 3GB RAM and 10K rpm drives and VS
2005 is much more responsive. But compared to VS 2003 IDE, VS 2005 IDE is
about 50 times slower.

If you go under Tools | Options | General -- you will find some options that
can speed up performance a little.

Rob.

 

[Alan Pretre]

This is just a thought, but back in the VS2002/2003 days, the context
sensitive help in VS would cause a slowdown and the solution was to
just disable the context sensitive help. Don't know if that will help,
but it might be worth a shot.

There might be a configuration of something that is hitting a network
location that is not available any more. The network access may be timing
out.

-- Alan

 

[clintonG]

Shameless braggart ;-)

I did notice one setting I've missed in the past, the useless and ridiculous
"Animate environment tools." Thanks for your comments Rob.

<%= Clinton Gallagher

 

[clintonG]

Thanks for your comments Chris and Alan. Disabling context sensitive help
sounds creative. I'll see what comes of it. I don't think network access is
involved. I have a good grip on centralized asset management but it too was
a good thought I hadn't considered.

What's strange is I've never seen the disk drive light up simply when
inserting a cursor into an editor.

<%= Clinton Gallagher

 

[Ken Cox - Microsoft MVP]

I'd contact Microsoft Support with that issue because it is certainly not
normal.

They have diagnostic tools that will analyze the events tell them what's
happening. Don't forget that your software comes with support incidents, In
this case, I'd be surprised if they count it against you because it is
basically a initial configuration problem.

Ken
MVP [ASP.NET]

 

[Leon Lambert]

I would reinstall it. Something sounds not right. I have even used it in
a virtual machine and it works fine. It is slightly slower than VS2003
but not enough to irritate me.

Leon Lambert