Cache Hit / Miss Rate Information
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5.6k
- Forks
- 1.6k
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
We're using the actions/cache action, and are trying to optimise its usage across many different actions.
One of the things which would be very helpful to understand is the hit/miss rate. While we can work it out by reading the output of an individual action, working out the cache rate on aggregate across many actions is harder.
We'd love to be able to see a cache hit/miss rate for different caches so we can determine if the caches are performing well or not.
Would this be possible to add?
Thanks,
Ed
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are identified in the issue. Start by reviewing the existing actions/cache outputs and how cache usage is represented across GitHub Actions, then define how aggregate hit/miss rates should be grouped and exposed; done means users can inspect rates for different caches.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, typescript
- Domain
- ci-cd, observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100