Why do compile/builds suddenly take so long?

[WSinc]

For some reason, the compile and build process now takes over 20 times as long to complete as

it did before.

I haven't made any changes to my computer, so I don't see why anything would be different.

The spyware doctor intelliguard is turned OFF, that didn't make any difference, and

I can't see any processes that might rob CPU time from the VS 2008 execuatables.

For example a compile of a short routine takes almost a minute, where it took only a couple of seconds before.

A build takes several minutes now, where it took a few seconds before.

Is there a way to goose up the priority of the VS 2008 executables? Maybe by using the process explorer,

or the task manager?

[Steven_L_Intel1]

Is it the compile itself or the link? Are you using any network shares for your sources? Does this happen even with a debug build?

[WSinc]

Both compiles and links are extremely slow.

No network resources.

Always use DEBUG, nothing else.

[WSinc]

I always use the DEBUG build, and I don't use any network resources.

That's why this is so puzzling - I've always done it the same way, so I don't see

why the behavior would suddenly be different.

The slowness occurs both with COMPILES and with the linker build.

I'm wondering if there is a "ghost" process somewhere that might be the one that grabs

mt.exe or the EXE I'm trying to build. mt.exe is from an intermediate process in the build.

I have noticed sometimes there are several copies of devenv.exe running at once. Is this normal?

Shouldn't there be just one?

Does your support group use a remote assist? Maybe I should contact them, because

if I upload anything, you won't have the same environment that I do, to test it with.

[Steven_L_Intel1]

Yes, we can do a remote assist. I suggest you open an issue with Intel Premier Support about it - ask that it be assigned to me.