| commit | f2512a0718f3a652ec536b513be82324361bbe77 | [log] [tgz] |
|---|---|---|
| author | Googler <tjgq@google.com> | Mon Feb 12 08:26:13 2024 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Mon Feb 12 08:28:01 2024 -0800 |
| tree | c8ba641c523ed10d227969165633c82846c12178 | |
| parent | 1f87fb4541756df61eb689d19eccb713d0808ad4 [diff] |
Optimize RemoteActionFileSystem#resolveSymbolicLinks by caching intermediate results in a trie. When scanning a filesystem tree, resolveSymbolicLinks does O(M*N) work, where M is the number of components in a file path and N is the number of files. This CL makes it O(M+N) instead. This makes large output tree artifacts (~250k files) much more efficient to scan (from ~45s to ~9s in a particular example; additional optimizations are possible and will be made in a followup CL). Related to https://github.com/bazelbuild/bazel/issues/17009. PiperOrigin-RevId: 606259673 Change-Id: Icf781a78b3271196e0029e3049d969a9e6073906
{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
