VS.NET Compiler performance

[Martin]

Is there a reason for (and hopefully a work-around to) the
VC++.NET's compiler "flushing" each output file to disk before compiling
the next one? I've noticed this in both the 2002 and 2003 releases.

The application in question is a normal unmanaged C++ MFC
application migrated from VC++ 6. There are many files in the project
(250-300+) but the majority are fairly small...

Unlike VC++6, it appears that the new compiler will only
start compiling the next file once the current file's output is
completely written to disk. I know this because

(a) the hard-disk is going crazy and
(b) the CPU is idling around 20% on average.

With VC++ 6 the CPU sat at basically 100% and
the disk light flashed now-and-then as the OS flushed lazily in the
background.

And it also appears to get slower and slower the further
into the compile (the CPU usage drops). It now takes about 3 times as
long to do a full compile as it did before...

A RAM disk definitely helps a lot but the one I have is 32MB
max and not enough to fit all of the files generated (upward of
70-80MB). Currently I can only fit the .OBJ files there, leaving .PCH,
..SBR, etc. files on the disk.

However I cannot see I should need to go to this extreme!!

Any help/suggestions welcome!

[Alon]

VS.NET Compiler performance

There is a help document about "Fast Compilation". You
might want to use the 'minimal rebuild' option.

Alon

You can incre[color=blue]
>-----Original Message-----
>Is there a reason for (and hopefully a work-around to) the
>VC++.NET's compiler "flushing" each output file to disk[/color]
before compiling[color=blue]
>the next one? I've noticed this in both the 2002 and 2003[/color]
releases.[color=blue]
>
>The application in question is a normal unmanaged C++ MFC
>application migrated from VC++ 6. There are many files in[/color]
the project[color=blue]
>(250-300+) but the majority are fairly small...
>
>Unlike VC++6, it appears that the new compiler will only
>start compiling the next file once the current file's[/color]
output is[color=blue]
>completely written to disk. I know this because
>
>(a) the hard-disk is going crazy and
>(b) the CPU is idling around 20% on average.
>
>With VC++ 6 the CPU sat at basically 100% and
>the disk light flashed now-and-then as the OS flushed[/color]
lazily in the[color=blue]
>background.
>
>And it also appears to get slower and slower the further
>into the compile (the CPU usage drops). It now takes[/color]
about 3 times as[color=blue]
>long to do a full compile as it did before...
>
>A RAM disk definitely helps a lot but the one I have is[/color]
32MB[color=blue]
>max and not enough to fit all of the files generated[/color]
(upward of[color=blue]
>70-80MB). Currently I can only fit the .OBJ files there,[/color]
leaving .PCH,[color=blue]
>..SBR, etc. files on the disk.
>
>However I cannot see I should need to go to this extreme!!
>
>Any help/suggestions welcome!
>
>.
>[/color]