Binary cache statistics
Nobody has claimed this yet.
- Dominant language
- PLpgSQL
- Stars
- 1.6k
- Forks
- 358
- Avg merge
- 20h 30m
- Merged PRs (30d)
- 27
Description
Hydra seems uniquely positioned to parse HTTP/S3 access logs to determine binary cache usage stats in human-meaningful terms. It seems like we could parse the S3 logs, see that a nar with some inscrutable hash had been requested, then map that back to the derivation and git revision that produced produced the inscrutable nar hash. Then we could present a nice download counter on the build page!
@edolstra I was inspired by https://github.com/NixOS/nixpkgs/commit/55e71f45cc10094edac3f66fb11682d2c8b0fd39, since it would be helpful to know how much people actually use the i686 nars.
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
The issue names no files, tests, or entry points. Start by locating Hydra's existing binary-cache handling and build-page data flow, then determine how access logs and NAR identifiers are represented. Done would mean presenting human-readable cache usage statistics, including download counts associated with builds or revisions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- analytics, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100