| commit | c428ee515380b90c9105df4b88bd397af9a84fd5 | [log] [tgz] |
|---|---|---|
| author | ulfjack <ulfjack@google.com> | Tue Jan 28 07:47:37 2020 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue Jan 28 07:48:32 2020 -0800 |
| tree | 1d973bbfd69cc52983f88374693fae4a5da505c5 | |
| parent | 63f0b36e61864cc805f50618ac72f76440ba4b84 [diff] |
Use a ForkJoinPool for async include scanning Previously, switching to a FJP was rolled back due to introducing a performance regression in some cases. While I was unable to reproduce the regression due to other changes in Bazel, this ties the switch to the async include scanner flag. I have carefully benchmarked that, and I think that switching to a FJP is required to roll out the async include scanner. PiperOrigin-RevId: 291931477
{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:
See CONTRIBUTING.md
