Robin Freyler

I found [this GitHub Actions](https://github.com/marketplace/actions/criterion-compare-prs) and will try to make it work for `wasmi`.

My personal summary is that https://github.com/marketplace/actions/criterion-compare-prs is not a fit to close the linked issue since the GitHub Actions unfortunately is heavily outdated and has outdated documentation which is a...

Did not want to close this issue but the linked PR: https://github.com/paritytech/wasmi/pull/324

Maybe running Criterion benchmarks on GitHub Actions CI is too noisy. The well known Cachegrind tool is made exactly for usage scenarios like these. The experimental (unreleased) [lai](https://bheisler.github.io/criterion.rs/book/iai/iai.html) tool from...

This is being worked on by @sergejparity here https://github.com/paritytech/wasmi/pull/422.

Implemented in https://github.com/paritytech/wasmi/pull/422. Closed.

We moved to Criterion based benchmarks that allow for more flexibility. I do not agree with a fixed benchmarking API as proposed in the initial comment since benchmarks are way...

Nowadays we do have a `wasmi_cli` tool (not yet published on crates.io). Therefore and also since this issue is quite dated I am going to close this issue for now....

@YellowApple I am currently cleaning up the issues list of `wasmi`. Is this feature still relevant to you? The problem is that `wasmi` is primarily used by Parity as an...

Thanks for the quick info! You'd probably need to reimplement this using the new `wasmi` engine though ... Closed.