| commit | d1f6b01a3e22c6c87ace6726acd1ef20c5821252 | [log] [tgz] |
|---|---|---|
| author | Benjamin Peterson <benjamin@python.org> | Thu Dec 03 23:40:31 2020 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Dec 03 23:42:12 2020 -0800 |
| tree | 2b15e7c74c94a7de9bc14ce045d16caeaee5f9f4 | |
| parent | 5a51814efdfbf89384a0e9542694b4f34e64bae6 [diff] |
Allow G1 for javac workers. G1 has a smoother memory profile than parallelGC, which is desirable for workers that users run locally like javac. Unfortunately, completely getting rid of the parallelGC option regresses Java build performance. This is because Turbine does not run as a worker—see https://github.com/bazelbuild/bazel/issues/8006—and G1 seems to do worse than parallelGC for short-lived programs. So, I simply moved the parallelGC option to the Turbine-specific jvm opts. I ran bazel-bench to test the performance this change building //src:bazel_nojdk: ``` metric mean median stddev pval wall: 475.842s ( -0.05%) 474.997s ( -0.09%) 1.203s 0.00000 cpu: 73.063s ( -2.28%) 72.980s ( -2.21%) 1.499s 0.40000 system: 19.427s ( +0.66%) 19.450s ( +1.09%) 0.111s 0.40000 memory: 89.667MB ( -0.74%) 90.000MB ( +0.00%) 0.471MB 0.00000 ``` Closes #12598. PiperOrigin-RevId: 345616260
{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
