CI‑Shaped Workflows: Store What Matters, Fail on What Counts

Description and use

Storing the full JSON artifact in CI enables job failures on any metric, not just the mean, providing transparent audit trails and post‑run analysis.

Problem

CI pipelines that only surface a mean value are blind to the real story of code performance; a single number can hide regressions, noise, or a broken measurement.

Outcome

Storing the full artifact turns CI from a black box into a transparent audit trail, enabling failure on the right metric and later investigation.

Workflow

• Ensure csperf is in PATH
• Run workload and capture artifact: csperf run --input examples/cpp/matrix_traversal.cpp --backend cpu --output results/ci.json
• Profile artifact: csperf profile results/ci.json --json

Evidence

Many teams run csperf run … in CI and only look at the printed mean.

Source

csperf lets you: Store the entire JSON artifact in your CI artifact store.

Source

Fail the job if any metric deviates beyond a threshold.

Source