
This includes uninstalling all add-ons and making sure that VS isn't configured to automatically open a project.

Turn off any features that could affect load time.Here's some things that might help people figure out what's going on: I understand the better compiler comes with some overhead, but what I see is a 300-500% compile time degradation - thats awful.Ĭould you maybe time some operations and post them so we get an idea what you mean by "slow"? On my machine, I wouldn't call VS 2005 slow, but if you compare it to notepad or my web browser it seems slow. While a faster machine may hide some of hide slow down, one could only wonder if Microsoft can optimize the compiler by offering options that disables unnecessary overhead references.

The VC8+ compiler executables/dlls are referencing sub-systems like crypto API, the Registry for some transparent reason and it is adding a tremendous amount of overhead to straight and pure compiles. ~1.0 secs with C2.DLL, _AbortCompilerPass()Īgain, this is just a compile, not a link. ~1.5 secs with OLE2.DLL, StringFromGUID2() Using DEPENDS to profile the two, I see 3 areas where the 5 seconds delays and time different are taking place: ~2.5 secs with ADVAPI32.DLL, CryptGetHashParam()

I see 1 seconds compiler under Vc6 and a 6 seconds compile under VS2005. Simply taking your obligatory "hello world" C/C++ program, just compile it, (CL /c helloword.cpp), #include Sure, faster machine, hides the poor performance quality of vs2005 but not all. I'm am seeing mixed results with faster machines.
