Moov OSS benchmarks

How to read this

• Each point is one CI run. The x-axis is the run date, not a hash from this hub repo.
• Click a row for the full series. Click a point on the chart to open that project commit on GitHub.
• Click a column header to sort. Click again to reverse. Missing values sink to the bottom.
• Latest and Previous are the two most recent runs. Δ prev is that step change.
• Change filter keeps benches that improved or worsened: trend vs median when there are 3+ runs, otherwise Δ prev. Unchanged rows are hidden.
• Trend is the full series (sparkline) and latest vs the median of the previous up to 10 runs, so one noisy job does not define the direction. Needs at least 3 runs. Red means slower / more memory / more allocs.
• Watchman already publishes from moov-io/watchman. ACH, cryptfs, and iso8583 now do the same in their own repos.
• Older ACH and cryptfs charts under bench/ach and bench/cryptfs are an archive. Those commit hashes belong to moov-io/benchmarks, not the libraries.

Add a library with the workflow in adding-a-project.md. Questions: oss@moov.io.