| commit | 01080982e9f97121292912b6db592127b41cde92 | [log] [tgz] |
|---|---|---|
| author | Googler <jhorvitz@google.com> | Mon Mar 06 06:14:07 2023 -0800 |
| committer | fweikert <fwe@google.com> | Fri Mar 17 14:06:08 2023 +0100 |
| tree | f092b4950b41a1e09321d7608e867e5bf2c3e052 | |
| parent | 0ce17480390cdced2df8d59249561613e81f446f [diff] |
Switch `RemoteFileArtifactValue` subclassing to optimize for memory cost. Adding `long expireAtEpochMilli` added 8 bytes to every `RemoteFileArtifactValue`, even ones without an expiration time. In contrast, `PathFragment materializationExecPath` is just a pointer so only costs 4 bytes, and since without it the cost is rounded up to the next multiple of 8 anyway (28 -> 32), it is free to add this field. Conveniently, since the expiration doesn't factor into `hashCode`/`equals`, it's actually simpler to arrange the classes this way. PiperOrigin-RevId: 514388630 Change-Id: I50a7e4e03b266f1a2dfad2fa38005c0c9a0cfa10
{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
