↓ Ir para o conteúdo principal

← todas as notas

📎 Webclip

How to make your build faster

The post argues that slow build feedback disrupts work, and says build times can be improved in several ways without buying SSDs. It focuses on smarter project layouts, parallel builds in Visual Studio and MSBuild, and the faster incremental builds available through Mighty Moose.

Reading notes
#

  • The author says long feedback cycles break concentration and make it hard to stay on task.
  • Smarter project layouts can help, and larger well-factored projects may build faster than many smaller ones.
  • Visual Studio and MSBuild already support parallel builds, and maxcpucount lets multiple projects build concurrently when dependencies allow it.
  • Parallel builds can improve times in some cases, but the author says the average gain is often only around 20–25%.
  • Mighty Moose uses more information than MSBuild because it knows what is changing and how that affects the dependency graph.
  • The author says static analysis can help decide whether public contracts changed and what tests need to run.
  • In the example given, Mighty Moose reduces an incremental build plus test discovery and test execution from about 4.5 seconds in MSBuild to about 2.5–3 seconds.
  • The feature is opt-in because compatibility with existing Visual Studio projects is the main concern.