Robin Freyler

I am closing this since the issue is pretty dated and the linked proof of concepts were made for the legacy engine that we no longer support. If this feature...

Glad I am not alone on this. So far I have used `cargo-flamegraph` to get some flamegraph data and try to make some sense out of the information it brought...

> PS: paritytech/polkadot#4311 claims 200-400% ish. Well that's absolutely the same that we see in `wasmi_v1` ... Looking forward to your updates. :sweat_smile:

Slowdown concerning configurations without `codegen-units=1` might be (partially) affected by https://github.com/rust-lang/rust/issues/46139.

> One more thing: Did you try `RUSTFLAGS='-C target-cpu=native'` yet? > It is only possible to define as env variable, not in the `Cargo.toml` AFAIK. I just tried it out...

Demonstrates how bad it really is: https://gist.github.com/Robbepop/ffa340bdfc306856a98e21597091f6f0

@athei Also ran the benchmarks on a different CPU and using the stable Rust compiler version 1.58. ``` Corei9-9900k@5GHZ rustc 1.58-stable ``` # Results ## Default Profile ``` compile_and_validate/v1 time:...

I tried to use custom package Cargo profiles for our Wasm `coremark` benchmarks between `wasmi_v0`, `wasmi_v1`, Wasm3 and Wasmtime that can be found [here](https://github.com/Robbepop/wasm-coremark-rs). On this profile ```toml [profile.release] lto...

Some `cargo flamegraph` execution runs show some very strange graphs for the slow case. The fast run shows a flamegraph as it is to be expected by the developer of...

@bjorn3 Thanks a lot for your comment! I tried adding ```toml [profile.bench] lto = "fat" [profile.release.package.wasmi_v1] codegen-units = 1 [profile.bench.package.wasmi_v1] codegen-units = 1 ``` To the root `Cargo.toml` of the...