https://github.com/boringcache/benchmark-hugo-go
Standalone Hugo GO benchmark runner for BoringCache vs GitHub Actions cache
https://github.com/boringcache/benchmark-hugo-go
Last synced: about 1 month ago
JSON representation
Standalone Hugo GO benchmark runner for BoringCache vs GitHub Actions cache
- Host: GitHub
- URL: https://github.com/boringcache/benchmark-hugo-go
- Owner: boringcache
- Created: 2026-04-27T11:36:40.000Z (about 2 months ago)
- Default Branch: main
- Last Pushed: 2026-05-13T10:19:52.000Z (about 1 month ago)
- Last Synced: 2026-05-13T12:28:21.909Z (about 1 month ago)
- Language: Shell
- Size: 96.7 KB
- Stars: 0
- Watchers: 0
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# benchmark-hugo-go
Public Hugo Go benchmark runner for BoringCache vs GitHub Actions cache.
This repo exists separately from [`boringcache/benchmarks`](https://github.com/boringcache/benchmarks) so the benchmark keeps:
- one pinned upstream source commit
- isolated GitHub Actions cache usage
- one per-repo BoringCache workspace name: `boringcache/benchmark-hugo-go`
- independent workflow history plus upstream-sync-driven benchmark runs and manual dispatches
## Source Model
- Upstream source lives in the pinned `upstream/` submodule.
Pinned upstream source:
- see committed `upstream/` submodule on `main`
## What It Measures
Fresh lane runs a no-prior-cache cold build plus one warm rerun for each backend:
- `cold`
- `warm1`
Rolling lane records the upstream commit build as-is after each upstream sync against the prior rolling cache and intentionally skips `warm1`.
The story this benchmark is meant to show is:
- speed on fresh cold and warm paths
- commit-build behavior on normal upstream syncs in the rolling lane
- storage footprint in each backend
- cache reuse through BoringCache's native Go `GOCACHEPROG` proxy path
## Cache Shape
BoringCache uses `boringcache/one` with `mode: go` for the native Go build-cache path and archives only `go-mod-cache` so module downloads stay comparable on fresh runners.
GitHub Actions cache stores:
- `GOMODCACHE`
- `GOCACHE`
## Token Model
This repo uses split BoringCache tokens as the standard CI shape:
- `BORINGCACHE_RESTORE_TOKEN` for read-only restore and proxy access
- `BORINGCACHE_SAVE_TOKEN` for trusted write paths
- `BORINGCACHE_API_TOKEN` only where a single bearer variable is still required for compatibility