performance optimization: copy with 128K blocks instead of 8K blocks

Before this change, using --spawn_strategy=sandboxed spends ?450ms for copying a
?80 MiB executable out of the sandbox into a FUSE file system we use to store
build artifacts.

A closer investigation revealed that cp(1) manages to copy the same file in only
175ms. The difference comes from cp(1) using a buffer size of 131072 bytes
(128K), which it takes from the st_blksize fstat(2) field (?Block size for
filesystem I/O?) of the output file system.

Guava hard-codes the buffer size to 8192 bytes, which results in many more FUSE
requests and a slower file transfer.

For non-FUSE file systems, this change should not have any adverse effects.

PiperOrigin-RevId: 293321468
1 file changed
tree: 16377fadc934caa8866b63935d0a652162f5d110
  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 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.

Getting Started

Documentation

Contributing to Bazel

See CONTRIBUTING.md

Build status