Triggering failed benchmarks

I was wondering if there would be a way to use this in the form of
- compare foo with bar, and if foo is 10% slower then bar fail the suite.

anothe useful way would be to fail a suite if performed less then x operations per second.

The issue names no files, tests, or entry points to begin with. First clarify the supported comparison and operations-per-second thresholds, how failures should be reported in CI, and which benchmark configuration should express them; done means both failure conditions are specified and covered by tests.

Written by the indexing model from the issue text.