Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(257)

Side by Side Diff: docs/linux_faster_builds.md

Issue 1318153003: [Docs] fixes (Closed) Base URL: https://chromium.googlesource.com/chromium/src@master
Patch Set: Created 5 years, 3 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View unified diff | Download patch
« no previous file with comments | « docs/linux_eclipse_dev.md ('k') | docs/linux_graphics_pipeline.md » ('j') | no next file with comments »
Toggle Intra-line Diffs ('i') | Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
OLDNEW
1 # Tips for improving build speed on Linux 1 # Tips for improving build speed on Linux
2 2
3 This list is sorted such that the largest speedup is first; see 3 This list is sorted such that the largest speedup is first; see
4 [Linux build instructions](linux_build_instructions.md) for context and 4 [Linux build instructions](linux_build_instructions.md) for context and
5 [Faster Builds](common_build_tasks.md) for non-Linux-specific techniques. 5 [Faster Builds](common_build_tasks.md) for non-Linux-specific techniques.
6 6
7 [TOC] 7 [TOC]
8 8
9 ## Use goma 9 ## Use goma
10 10
11 If you work at Google, you can use goma for distributed builds; this is similar 11 If you work at Google, you can use goma for distributed builds; this is similar
(...skipping 125 matching lines...) Expand 10 before | Expand all | Expand 10 after
137 137
138 ## Using tmpfs 138 ## Using tmpfs
139 139
140 You can use tmpfs for the build output to reduce the amount of disk writes 140 You can use tmpfs for the build output to reduce the amount of disk writes
141 required. I.e. mount tmpfs to the output directory where the build output goes: 141 required. I.e. mount tmpfs to the output directory where the build output goes:
142 142
143 As root: 143 As root:
144 144
145 mount -t tmpfs -o size=20G,nr_inodes=40k,mode=1777 tmpfs /path/to/out 145 mount -t tmpfs -o size=20G,nr_inodes=40k,mode=1777 tmpfs /path/to/out
146 146
147 *** note
147 **Caveat:** You need to have enough RAM + swap to back the tmpfs. For a full 148 **Caveat:** You need to have enough RAM + swap to back the tmpfs. For a full
148 debug build, you will need about 20 GB. Less for just building the chrome target 149 debug build, you will need about 20 GB. Less for just building the chrome target
149 or for a release build. 150 or for a release build.
151 ***
150 152
151 Quick and dirty benchmark numbers on a HP Z600 (Intel core i7, 16 cores 153 Quick and dirty benchmark numbers on a HP Z600 (Intel core i7, 16 cores
152 hyperthreaded, 12 GB RAM) 154 hyperthreaded, 12 GB RAM)
153 155
154 * With tmpfs: 156 * With tmpfs:
155 * 12m:20s 157 * 12m:20s
156 * Without tmpfs 158 * Without tmpfs
157 * 15m:40s 159 * 15m:40s
OLDNEW
« no previous file with comments | « docs/linux_eclipse_dev.md ('k') | docs/linux_graphics_pipeline.md » ('j') | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698