| commit | d5c4f551fa9f5981b36ab67c69386e3787d06f0c | [log] [tgz] |
|---|---|---|
| author | larsrc <larsrc@google.com> | Thu Jan 20 00:18:58 2022 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Jan 20 00:20:31 2022 -0800 |
| tree | 65f622621697c8bcab55c970d8e51b15c2402cac | |
| parent | f7119d3fdd54d995540c23e1488278ad1ba846e0 [diff] |
Add new flag `--experimental_dynamic_local_load_factor`. This controls how much load dynamic execution will put on the local machine when seeing a large number of actions. This flag deprecates `--experimental_dynamic_execution_cpu_limited`. Passing `--experimental_dynamic_local_load_factor=1` is equivalent to passing `--experimental_dynamic_execution_cpu_limited`, and passing `--experimental_dynamic_local_load_factor=0` is equivalent to passing `--noexperimental_dynamic_execution_cpu_limited` (the default). A value between 0 and 1 (exclusive) affects the amount of local actions we allow from dynamic execution at a time when under load, with a higher number meaning more actions. A large number of actions waiting to be executed locally is an indicator of high load, up to the number jobs, and will cause a reduction in how many actions we run locally, scaled by this flag. Yes, it seems counterintuitive that we allow fewer resources under high load, but when we have a large number of actions, the remote system will do most of the work, and there is little to be gained from putting load on the local machine. This flag also mostly obviates `--experimental_dynamic_skip_first_build`, though we want to run more real-world tests before we deprecate that flag. PiperOrigin-RevId: 422997952
{Fast, Correct} - Choose two
Build and test software of any size, quickly and reliably.
Speed up your builds and tests: Bazel rebuilds only what is necessary. With advanced local and distributed caching, optimized dependency analysis and parallel execution, you get fast and incremental builds.
One tool, multiple languages: Build and test Java, C++, Android, iOS, Go, and a wide variety of other language platforms. Bazel runs on Windows, macOS, and Linux.
Scalable: Bazel helps you scale your organization, codebase, and continuous integration solution. It handles codebases of any size, in multiple repositories or a huge monorepo.
Extensible to your needs: Easily add support for new languages and platforms with Bazel's familiar extension language. Share and re-use language rules written by the growing Bazel community.
Follow our tutorials:
To report a security issue, please email security@bazel.build with a description of the issue, the steps you took to create the issue, affected versions, and, if known, mitigations for the issue. Our vulnerability management team will respond within 3 working days of your email. If the issue is confirmed as a vulnerability, we will open a Security Advisory. This project follows a 90 day disclosure timeline.
See CONTRIBUTING.md
