Speed of build with/without output window
 

Has anyone done metrics on whether a typical build via VB will run measureably faster if the build output window is not present, compared to when it is present and showing all of the build actions?

We run a bunch of builds on virtual machines, and my boss has said that previous testing indicated that the builds went faster with the output window absent, but my measurements do not support those results. There is a lot of screen scolling going on (i.e. all files extracted from source control at the beginning of the build are listed on the output window from the extract script), but from what I've seen VB does a pretty good job of buffering output and things continue to run normally even if the display is lagging behind.

Thanks!
Scott

You can run the build on the command line. It does speed things up a bit. Only problem is that if the build fails, you can not start the build again from the failed step through the command line interface.