commit | 33a6b9a8477f70b31441d99758ff3cede9d0c926 | [log] [tgz] |
---|---|---|
author | Googler <chiwang@google.com> | Thu Jan 16 02:17:35 2025 -0800 |
committer | Copybara-Service <copybara-worker@google.com> | Thu Jan 16 02:19:03 2025 -0800 |
tree | 7750e556984cbb074e803b0bacb1508cacf85dab | |
parent | e53072135552ee2880f117fbfa41c3525d0330ca [diff] |
Fix performance regression in CriticalPathComputer. Previously, when actions are change pruned, we add their entire transitive closure to critical path graph. This could slow down incremental builds if the action graph is large and only a small portion of it is invalidated. This CL improves that by only adding actions that are invalidated (including change pruned). We achieve that by updating Skyframe to emit change pruning event. These event are only emitted for nodes that were invalidated by dirtiness check during incremental builds. So that the CriticalPathComputer now operates on a subset of action graph that only contains dirty actions. This is more correct and performant for incremental builds. PiperOrigin-RevId: 716146196 Change-Id: I71add4240458b5d4087b1af81a41202f98fee947
{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