OLD | NEW |
(Empty) | |
| 1 #summary tips for improving build speed on Linux |
| 2 #labels Linux,build |
| 3 |
| 4 This list is sorted such that the largest speedup is first; see LinuxBuildInstru
ctions for context and [Faster Builds](https://code.google.com/p/chromium/wiki/C
ommonBuildTasks#Faster_Builds) for non-Linux-specific techniques. |
| 5 |
| 6 |
| 7 |
| 8 ## Use goma |
| 9 |
| 10 If you work at Google, you can use goma for distributed builds; this is similar
to [distcc](http://en.wikipedia.org/wiki/Distcc). See [go/ma](http://go/ma) for
documentation. |
| 11 |
| 12 Even without goma, you can do distributed builds with distcc (if you have access
to other machines), or a parallel build locally if have multiple cores. |
| 13 |
| 14 Whether using goma, distcc, or parallel building, you can specify the number of
build processes with `-jX` where `X` is the number of processes to start. |
| 15 |
| 16 ## Use Icecc |
| 17 |
| 18 [Icecc](https://github.com/icecc/icecream) is the distributed compiler with a ce
ntral scheduler to share build load. Currently, many external contributors use i
t. e.g. Intel, Opera, Samsung. |
| 19 |
| 20 When you use Icecc, you need to set some gyp variables. |
| 21 |
| 22 **linux\_use\_bundled\_binutils=0** |
| 23 |
| 24 -B option is not supported. [relevant commit](https://github.com/icecc/icecream/
commit/b2ce5b9cc4bd1900f55c3684214e409fa81e7a92) |
| 25 |
| 26 **linux\_use\_debug\_fission=0** |
| 27 |
| 28 [debug fission](http://gcc.gnu.org/wiki/DebugFission) is not supported. [bug](ht
tps://github.com/icecc/icecream/issues/86) |
| 29 |
| 30 **clang=0** |
| 31 |
| 32 Icecc doesn't support clang yet. |
| 33 |
| 34 ## Build only specific targets |
| 35 |
| 36 If you specify just the target(s) you want built, the build will only walk that
portion of the dependency graph: |
| 37 ``` |
| 38 $ cd $CHROMIUM_ROOT/src |
| 39 $ ninja -C out/Debug base_unittests |
| 40 ``` |
| 41 |
| 42 ## Linking |
| 43 ### Dynamically link |
| 44 |
| 45 We normally statically link everything into one final executable, which produces
enormous (nearly 1gb in debug mode) files. If you dynamically link, you save a
lot of time linking for a bit of time during startup, which is fine especially
when you're in an edit/compile/test cycle. |
| 46 |
| 47 Run gyp with the `-Dcomponent=shared_library` flag to put it in this configurati
on. (Or set those flags via the `GYP_DEFINES` environment variable.) |
| 48 |
| 49 e.g. |
| 50 |
| 51 ``` |
| 52 $ build/gyp_chromium -D component=shared_library |
| 53 $ ninja -C out/Debug chrome |
| 54 ``` |
| 55 |
| 56 See the [component build page](http://www.chromium.org/developers/how-tos/compon
ent-build) for more information. |
| 57 |
| 58 ### Linking using gold |
| 59 |
| 60 The experimental "gold" linker is much faster than the standard BFD linker. |
| 61 |
| 62 On some systems (including Debian experimental, Ubuntu Karmic and beyond), there
exists a `binutils-gold` package. Do not install this version! Having gold as t
he default linker is known to break kernel / kernel module builds. |
| 63 |
| 64 The Chrome tree now includes a binary of gold compiled for x64 Linux. It is use
d by default on those systems. |
| 65 |
| 66 On other systems, to safely install gold, make sure the final binary is named `l
d` and then set `CC/CXX` appropriately, e.g. `export CC="gcc -B/usr/local/gold/b
in"` and similarly for `CXX`. Alternatively, you can add `/usr/local/gold/bin` t
o your `PATH` in front of `/usr/bin`. |
| 67 |
| 68 ## WebKit |
| 69 ### Build WebKit without debug symbols |
| 70 |
| 71 WebKit is about half our weight in terms of debug symbols. (Lots of templates!)
If you're working on UI bits where you don't care to trace into WebKit you can
cut down the size and slowness of debug builds significantly by building WebKit
without debug symbols. |
| 72 |
| 73 Set the gyp variable `remove_webcore_debug_symbols=1`, either via the `GYP_DEFIN
ES` environment variable, the `-D` flag to gyp, or by adding the following to `~
/.gyp/include.gypi`: |
| 74 ``` |
| 75 { |
| 76 'variables': { |
| 77 'remove_webcore_debug_symbols': 1, |
| 78 }, |
| 79 } |
| 80 ``` |
| 81 |
| 82 ## Tune ccache for multiple working directories |
| 83 |
| 84 (Ignore this if you use goma.) |
| 85 |
| 86 Increase your ccache hit rate by setting `CCACHE_BASEDIR` to a parent directory
that the working directories all have in common (e.g., `/home/yourusername/devel
opment`). Consider using `CCACHE_SLOPPINESS=include_file_mtime` (since if you a
re using multiple working directories, header times in svn sync'ed portions of y
our trees will be different - see [the ccache troubleshooting section](http://cc
ache.samba.org/manual.html#_troubleshooting) for additional information). If yo
u use symbolic links from your home directory to get to the local physical disk
directory where you keep those working development directories, consider putting |
| 87 ``` |
| 88 alias cd="cd -P" |
| 89 ``` |
| 90 in your .bashrc so that `$PWD` or `cwd` always refers to a physical, not logical
directory (and make sure `CCACHE_BASEDIR` also refers to a physical parent). |
| 91 |
| 92 If you tune ccache correctly, a second working directory that uses a branch trac
king trunk and is up-to-date with trunk and was gclient sync'ed at about the sam
e time should build chrome in about 1/3 the time, and the cache misses as report
ed by `ccache -s` should barely increase. |
| 93 |
| 94 This is especially useful if you use `git-new-workdir` and keep multiple local w
orking directories going at once. |
| 95 |
| 96 ## Using tmpfs |
| 97 |
| 98 You can use tmpfs for the build output to reduce the amount of disk writes requi
red. I.e. mount tmpfs to the output directory where the build output goes: |
| 99 |
| 100 As root: |
| 101 * `mount -t tmpfs -o size=20G,nr_inodes=40k,mode=1777 tmpfs /path/to/out` |
| 102 |
| 103 **Caveat:** You need to have enough RAM + swap to back the tmpfs. For a full deb
ug build, you will need about 20 GB. Less for just building the chrome target or
for a release build. |
| 104 |
| 105 Quick and dirty benchmark numbers on a HP Z600 (Intel core i7, 16 cores hyperthr
eaded, 12 GB RAM) |
| 106 |
| 107 | With tmpfs: | 12m:20s | |
| 108 |:------------|:--------| |
| 109 | Without tmpsfs: | 15m:40s | |
OLD | NEW |