Open froydnj opened 4 years ago
Related: https://github.com/mozilla/sccache/issues/552 .
IIRC the zip file cache entry format dates back to the original Python version of sccache. I don't know that inventing a custom format is worthwhile, but just switching to zstd-compressed tarballs ought to be a pretty simple change.
The bazel remote execution api's ActionResult protobuf message might be worth considering over tarballs. It provides a bit more structure, and is flexible enough to handle multiple output files (which would be good to support for C/C++ compiles too). It would also make it easier to integrate with REAPI cache servers.
Zip files are super-convenient, but maybe using something that would provide a better compression/performance ratio would be better. At least in the common case for C/C++ compiles where you have a single output and no compiler messages. Maybe you could invent a small custom format for the typical Rust compile (three outputs) as well.