commit | ed79a0f459b043b27e208e162b70f09a15a115ac | [log] [tgz] |
---|---|---|
author | Googler <lberki@google.com> | Thu Apr 11 00:38:00 2024 -0700 |
committer | Copybara-Service <copybara-worker@google.com> | Thu Apr 11 00:39:35 2024 -0700 |
tree | 4166769651c09a508fe3aa925073970f9f78a203 | |
parent | 750a0389780c9eff49e1ede7647e28949b1996b7 [diff] |
Implement a "transitive" mode for memory dumping. It dumps every object in the Skyframe transitive closure of a SkyValue. Currently, it's very inefficient for multiple reasons: * ConcurrentIdentitySet is slow when accessed from many threads. It should be sharded. * MemoryAccountant cannot be accessed concurrently, so it's protected with a monitor. We should collect the numbers separately for each SkyValue and merge them later. But at least the implementation of processTransitive() is pretty neat -- mirroring the Skyframe graph with a graph of CompletableFuture instances. RELNOTES: None. PiperOrigin-RevId: 623734658 Change-Id: I2eb43ac1ad30a831d1ffb524bc0f4352e3fe7872
{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