Skip to content

docs(results): the results README says what is published instead of 'no data yet' (release-gated) #109

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
FumingPower3925 wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

docs(results): the results README says what is published instead of 'no data yet' (release-gated) #109

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 7 additions & 3 deletions results/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,14 +4,18 @@ Machine-generated benchmark data for [goceleris/celeris](https://github.com/goce
published by [goceleris/probatorium](https://github.com/goceleris/probatorium)'s
`mage Publish` after each cluster benchmark run.

**There may be no data here yet** — the first results land when the benchmark
tier runs on the cluster.
**What is published.** `ls results/` lists the versions: at the time of writing
v1.5.5 to v1.5.8, with the latest run at `results/v1.5.8/20260829/` (both
`x86_64` and `arm64`, one 90 s run per cell). A celeris release that has not been
through the benchmark tier has no directory here, so a version's absence means
"not benchmarked", not "no data yet". The dashboard shows the versions this tree
holds, minus the versions in `DEACTIVATED_VERSIONS` ([`scripts/build-data.ts`](../scripts/build-data.ts)).

## Layout

```
results/
<version>/ # e.g. v1.4.15
<version>/ # e.g. v1.5.8
<yyyymmdd>/ # run date
<arch>/ # x86_64 | arm64
summary.json # per-(scenario × server) aggregates (rps, latency pctls, RSS, CPU)
Expand Down
Loading