`bench-deploy`: Convert between Criterion JSON formats

Open
#52 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
github-actions
Domain
ci-cd

Research direction

Trace the existing gh-pages and commit-comment benchmark workflow paths and inspect the Criterion JSON formats they produce. Use jq to define the conversion between those formats, then verify that one benchmark per commit can support criterion-table, plots, and deployment without separate reruns.

Written by the indexing model from the issue text.

Description

After #44

Currently, our gh-pages benchmark JSONs can't be used with criterion-table and our commit-comment benchmarks can't be used in plots. After some testing I've found that reformatting the JSON files is fairly straightforward using jq. This would have several benefits:

  • Run only one benchmark per commit, rather than fiddling with env vars to produce several for use in our various comparison tools. This saves time and UX hassle
  • Cached commit-comment benchmarks could be immediately deployed when a PR is merged, rather than having to re-run the benchmark in the gh-pages format for plotting & deployment. This saves time, runner resources and clutter in gh-pages
Dominant language
No language data
Stars
0
Forks
3
Avg merge
59m
Merged PRs (30d)
2

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from argumentcomputer/ci-workflows

All issues in argumentcomputer/ci-workflows

Similar issues

More DevOps issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.