| commit | f057c7408a60cb9955a95d02e9e9a05760bd1f13 | [log] [tgz] |
|---|---|---|
| author | Googler <jhorvitz@google.com> | Thu Mar 09 13:08:33 2023 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Mar 09 13:09:52 2023 -0800 |
| tree | 26fd3549720d0ae21682c15c834bac43b5b33048 | |
| parent | caf5253486ea4c47ff360a0d4caa46cc0129fcac [diff] |
Use smart subclassing in `ActionExecutionValue` to save memory. There are currently four fields in `ActionExecutionValue`: 1. `ImmutableMap` for file outputs 2. `ImmutableMap` for tree artifact outputs 3. `ImmutableList` for fileset output symlinks 4. `NestedSet` for discovered modules However, some of these fields are mutually exclusive, and some only occur with a single file output. Subclasses are created for each distinct category of action. The majority of the memory savings in this change come from the `SingleOutputFile` class, which is used for the vast majority of actions. It saves memory by storing the single `Artifact` and `FileArtifactValue` as fields without even using a `Map`. Actions which output multiple files or trees still retain an `ImmutableMap`, but for those, additional memory is saved by using `Map#forEach` for iteration instead of `Map#entrySet`, which instantiates and retains a reference to the entry set. Some unit tests had to be cleaned up to match the newly enforced preconditions checks. Serialization tests for `ActionExecutionValue` are moved to `ActionExecutionValueTest`. PiperOrigin-RevId: 515420002 Change-Id: If4b84ee938a715733bcd817a7e70a1493413588e
{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
