3 ms·
Bazel is the best system which I have ever used.
by solomatov 8y ago
Bazel is the best system which I have ever used.
- adev_ 8y agoLucky you, I never met a user outside of Google that like it.
- solomatov 8y agoI am not a Google employee. There're several reasons why it worked so well for us: - It can take advantage of many cores which you have in your computers. - It's polyglot. We have several languages in our project, and mixing several build systems were a nightmare. - It's correct. Very rarely you really need to run clean builds. It has its learning curve, but once you got it, you start to love it.
- curiousgal 8y ago>it can take advantage of many cores which you have in your computers. Which is a bad thing when you're on a shared server. I remember it wasn't straightforward to limit the number of cores it utilizes and it even ignored the flag I passed it. I eventually resorted to waiting until the weekend when no one in the lab was running jobs.
- maccam94 8y agoOuch. For a workaround in the future, maybe you can lower the priority of your bazel server via nice/renice?
- grandmczeb 8y agoDoes “--jobs N” not work?
- jmmv 8y agoUnfortunately not. "--jobs N" limits the parallelism during the execution phase (when Bazel executes compilers, etc.) but doesn't limit the parallelism of the analysis phase (when Bazel loads BUILD files and constructs the build graph). For the latter there is a "--loading_phase_threads N" flag. We are actively trying to make Bazel better use the local resources, and also clean up the current mess that the flags are in this area. See the discussion at https://groups.google.com/d/msg/bazel-dev/7pcrJY6Xo78/JDe256-tBQAJ https://groups.google.com/d/msg/bazel-dev/7pcrJY6Xo78/JDe256... for some context.
- laurentlb 8y agoIf you still have a problem, please file a bug. We can look at it. (I work on Bazel)