StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>We also have huge solutions. Build and compilation is all about I/O.</p> <p><strong>Solid-state drives</strong> are very promising. A co-worker put a solid-state drive in his laptop, and found that it is now much faster than his humongous main development box. Don't have the details, but he claims many times faster.</p> <p>We've been fiddling with <strong>solution folders</strong> to group parts of the project: This makes it easier for devs to <strong>unload projects they aren't working on</strong>.</p> <p><strong><code>/m</code> rarely helps with .NET debug builds</strong>. I ran a series of tests on this a few weeks ago and found minor differences. Findings:</p> <ul> <li>Because my build is I/O constrained, using <strong>/m:2-4</strong> makes debug builds <strong>slower</strong> for me.</li> <li>Release builds usually much faster.</li> <li>Code analysis adds a lot of time.</li> </ul> <p>Big picture: In reality, compilation is a pretty minor cost for me, compared to getting source and running unit tests. On our build server, the integration tests and packaging are almost all the time. For my development box, I schedule a batch file that gets source, builds, runs unit tests before I come to work and while I'm at lunch. Good enough.</p> <p>On the build server, it's more complicated. We're thinking of setting up chained parallel <a href="http://en.wikipedia.org/wiki/CruiseControl" rel="nofollow noreferrer">CruiseControl.NET</a> builds on various machines. We are using VSTS build, but it is too expensive (and time consuming) to scale horizontally like this.</p> <p>My numbers for detail-oriented folks. Configurations from slowest to fastest, running msbuild "bigsolution.sln" /target:clean - between each.</p> <ol> <li>/m: 4, Debug with code analysis 1:38</li> <li>/m: 1, Debug with code analysis 1:30</li> <li>/m: 4, Debug with no code analysis 1:30</li> <li>/m: 1, Debug with no code analysis 1:30</li> <li>/m: 1, Release with code analysis: 1:30</li> <li>/m: 4, Release with code analysis: 1:05</li> <li>/m: 4, Release with no code analysis: 0:53</li> </ol> <p>Build time without rebuild or clean: ~ 4-10 seconds</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload