commit | a0a72265ea37270c110630f528127e18939f4016 | [log] [tgz] |
---|---|---|
author | Alexander Golovlev <golovlev@gmail.com> | Tue Oct 29 04:26:22 2024 -0700 |
committer | Copybara-Service <copybara-worker@google.com> | Tue Oct 29 04:27:59 2024 -0700 |
tree | 3d137d748163ab9f7a10f3977c1746474b042a4d | |
parent | ba86658080fd8940334e66a5426ecbf5c630f322 [diff] |
Performance optimization for isSymbolicLink() calls on Windows Current implementation for WindowsFileSystem.isSymbolicLink() makes unnecessary system calls which significantly affect the performance. Original code goes through the following: - AbstractFileSystemWithCustomStat.isSymbolicLink - WindowsFileSystem.stat - WindowsFileSystem.getIoFile - JavaIoFileSystem.getNioPath - Files.readAttributes - WindowsFileSystem.fileIsSymbolicLink - WindowsFileOperations.getLastChangeTime This implementation skips most of them. Closes #24047. PiperOrigin-RevId: 690964117 Change-Id: I2b407d9c69af62e770684d868d04e60d7ce1773e
{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