Google Git
Sign in
bazel / bazel / 01e6e05a35633df92cafc20b28eac15cd1aefa09
commit01e6e05a35633df92cafc20b28eac15cd1aefa09[log] [tgz]
authorBenjamin Peterson <bp@benjamin.pe>Wed Jul 03 03:13:55 2019 -0700
committerCopybara-Service <copybara-worker@google.com>Wed Jul 03 03:14:56 2019 -0700
tree5b5631a3dd66762b4524022c7c19fd8d323bb888
parent11e03574d2afa977d4319589a9c043f73718d904 [diff]
Enable G1 for Bazel and the Java host toolchain.

3842bd39e10612c7eef36c6048407e81bcd0a8fb disabled G1 for Bazel itself as well as the javac workers. At that time, Bazel was using an embedded JDK 9. Now, Bazel uses Java 11, so it's worth reconsidering the choice. In particular, the introduction of parallel full G1 GC in Java 10 addressed G1 throughput issues.

I tried to replicate the benchmarks mentioned by 3842bd39e10612c7eef36c6048407e81bcd0a8fb and couldn't see any difference between G1 and the Old Parallel GC. (3842bd39e10612c7eef36c6048407e81bcd0a8fb is not clear about the experimental protocol. My approach was to do an initial build of the target and then run "clean" between each measurement.) Additionally, on my machine, java8 and java11 startup times are within 10ms of each other.

Further in G1's favor is some internal experience. We have targets that either OOM or fall into the slow full gc death march with the Old Parallel GC but do fine under G1.

Closes #8423.

PiperOrigin-RevId: 256334384
2 files changed
tree: 5b5631a3dd66762b4524022c7c19fd8d323bb888
  1. .bazelci/
  2. examples/
  3. scripts/
  4. site/
  5. src/
  6. third_party/
  7. tools/
  8. .bazelrc
  9. .gitattributes
  10. .gitignore
  11. AUTHORS
  12. BUILD
  13. CHANGELOG.md
  14. CODEOWNERS
  15. combine_distfiles.py
  16. combine_distfiles_to_tar.sh
  17. compile.sh
  18. CONTRIBUTING.md
  19. CONTRIBUTORS
  20. distdir.bzl
  21. ISSUE_TEMPLATE.md
  22. LICENSE
  23. README.md
  24. WORKSPACE
README.md

Bazel

{Fast, Correct} - Choose two

Build and test software of any size, quickly and reliably.

  • Speed up your builds and tests: Bazel only rebuilds 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.

Getting Started

Documentation

Contributing to Bazel

See CONTRIBUTING.md

Build status

Bazel is released in ‘Beta’. See the product roadmap to learn about the path toward a stable 1.0 release.