Skip to content

Conversation

Mousius
Copy link
Contributor

@Mousius Mousius commented Apr 28, 2023

This is a proof of concept, for moving the benchmark suite to use nanobench, which is a single header file but has advantages over the existing benchmark suite:

  • Robustness - nanobench will explicitly tell you when benchmarks are unstable, and offer some guidance to help stabilise them.
  • JSON Output - this should allow us to store the results in a more machine friendly format, in future we can integrate this into CI to do checks on PRs

I also looked at Google Benchmark and Catch2, but nanobench was more appealing due to minimal integration requirements with the existing hybrid build architecture.

Mousius added 2 commits April 28, 2023 10:35
This is a proof of concept, for moving the benchmark suite to use
[nanobench](https://github.com/martinus/nanobench.git), which is a
single header file but gives some great advantages over the existing
benchmark suite:

* Robustness - nanobench will explicitly tell you when benchmarks are
  unstable, and offer some guidance to help stabilise them.
* JSON Output - this should allow us to store the results in a more
  machine friendly format, in future we can integrate this into CI to do
  checks on PRs
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant