@@ -151,14 +151,23 @@ RBE builds can be slow for a few different reasons. The most common reason is
151151likely to be that the remote caches are cold. When the caches are warm, a
152152compile step consists only of downloading the compiled TU from the cache. When
153153the caches are cold, the remote workers must run the compilation commands,
154- which takes more time.
154+ which takes more time. If the worker pool is overloaded, compile commands may
155+ run locally instead, which will also be slower.
155156
156157RBE builds can also be slow if your network connection is bandwidth constrained.
157158Anecdotally, even with a warm cache, I have noticed slow builds from home due
158159to RBE saturating my low-tier Comcast Business connection.
159160
161+ For Googlers on a corp macOS device, both RBE and non-RBE builds can be slow
162+ due to various background and monitoring processes running. See
163+ [ here] ( https://buganizer.corp.google.com/issues/324404733#comment16 ) for how
164+ to disable some of them. You should also disable Spotlight scanning of the
165+ engine source directory as described
166+ [ here] ( go/building-chrome-mac#add-the-source-directory-to-the-spotlight-privacy-list ) .
167+
160168When RBE builds are slow, non-RBE builds may be faster, especially incremental
161- builds.
169+ builds. You can disable remote builds without invalidating your existing build
170+ by setting the environment variable ` RBE_exec_strategy=local ` .
162171
163172### Proxy status and debug logs
164173
0 commit comments