View local cache hits and compare against remote cache hits

[alexander-scott]

Description of the problem / feature request:

I would like to see in the bazel status/info line the local cache hits printed alongside the remote cache hits.

Feature requests: what underlying problem are you trying to solve with this feature?

For solutions which involve a constantly changing local_cache/output_base, it would be useful to know how effective/up-to-date the local cache currently is. In this scenario, if the current local cache had few local cache hits for a bazel command but many remote cache hits or linux sandbox processes, the state of the local cache would need to be investigated. Currently the only way to estimate the effectiveness of a local_cache is via looking at timestamps, i.e. how long ago was the bazel command run that produced the local_cache.

What operating system are you running Bazel on?

Ubuntu

What's the output of bazel info release?

release 3.7.0

Have you found anything relevant by searching the web?

Nothing that seems to meet the request unfortunately. On this page https://docs.bazel.build/versions/master/remote-caching-debug.html#checking-your-cache-hit-rate, it mentions Local cache hits are not included in this summary, leading me to create this feature request to include it in this summary.

[philwo]

I'm not sure what "local cache hits" even means here. 🤔 Does this refer to the --disk_cache= feature?

[alexander-scott]

No with "local cache hits" I meant just the regular build outputs stored on a local machine after building. I want to know how often these are reused compared to remote cache hits and local action execution.

[github-actions]

Thank you for contributing to the Bazel repository! This issue has been marked as stale since it has not had any activity in the last 2+ years. It will be closed in the next 14 days unless any other activity occurs or one of the following labels is added: "not stale", "awaiting-bazeler". Please reach out to the triage team (@bazelbuild/triage) if you think this issue is still relevant or you are interested in getting the issue resolved.