commit | 5bdb4ca1a5215ee5b1276865fcc7cf068ca0ced8 | [log] [tgz] |
---|---|---|
author | Colin Cross <ccross@android.com> | Tue Apr 14 17:22:19 2015 -0700 |
committer | Colin Cross <ccross@android.com> | Wed Apr 15 11:03:17 2015 -0700 |
tree | 64133a2c567e272c113e965c9f7f3bae89ee7be6 | |
parent | 8c1c6c03f8ad3e1267c047b83d6e7262de989c73 [diff] |
Set GOMAXPROCS to number of CPUs Apparently Go only allows a single thread to be executing by default, so the increase in performance seen when concurrency was added to Blueprint was entirely due to scheduling goroutines while the executing goroutine was blocked in a syscall. Whoops. Set GOMAXPROCS to the number of CPUs. Reduces wall thime by >2x on one workload. Change-Id: Ib5fc7761c09a076fc5a1b7f08f5ccf034304477c
Blueprint is a meta-build system that reads in Blueprints files that describe modules that need to be built, and produces a Ninja manifest describing the commands that need to be run and their dependencies. Where most build systems use built-in rules or a domain-specific language to describe the logic for converting module descriptions to build rules, Blueprint delegates this to per-project build logic written in Go. For large, heterogenous projects this allows the inherent complexity of the build logic to be maintained in a high-level language, while still allowing simple changes to individual modules by modifying easy to understand Blueprints files.