Storage-Optimized Disk Cache For Multiple On-Host Instances of Same Repo
Description of the feature request:
I am wondering if it is possible to have disk caches symlink/hardlink content into repositories' output bases rather than direct copy the contents. The intent of this is to reduce overall storage space used by all parts of a Bazel project, especially when there are multiple instances of the same repository on a single machine, each with their own local Bazel cache as you might have with a CI system.
Which category does this issue belong to?
Performance
What underlying problem are you trying to solve with this feature?
We run CI machines with 10-50 agents on the same machine. This leads to a lot of content duplicated across the various agents' output bases and local cache. Having smarter storage-optimized configurations that reduce the overall disk footprint of Bazel would be incredibly helpful.
Which operating system are you running Bazel on?
Linux
What is the output of bazel info release?
No response
If bazel info release returns development version or (@non-git), tell us how you built Bazel.
No response
What's the output of git remote get-url origin; git rev-parse HEAD ?
Have you found anything relevant by searching the web?
No
Any other information, logs, or outputs that you want to share?
No response
Please give --repo_contents_cache a try - it shares repos across workspaces by symlinking into a central cache.
Please reopen if Fabian's suggestion above does not meet your requirements.