abrown opened PR #11733 from abrown:bench-compile to bytecodealliance:main:
Provides a simple way to measure compilation time across a set of compiler scenarios. Like the
instantiationbenchmark, this allows dropping in new benchmarks to add to the benchmark suite; e.g.,ln -s $(realpath .../benchmark.wasm) benches/compile/benchmark.wasm.<!--
Please make sure you include the following information:
If this work has been discussed elsewhere, please include a link to that
conversation. If it was discussed in an issue, just mention "issue #...".Explain why this change is needed. If the details are in an issue already,
this can be brief.Our development process is documented in the Wasmtime book:
https://docs.wasmtime.dev/contributing-development-process.htmlPlease ensure all communication follows the code of conduct:
https://github.com/bytecodealliance/wasmtime/blob/main/CODE_OF_CONDUCT.md
-->
abrown requested fitzgen for a review on PR #11733.
abrown requested wasmtime-default-reviewers for a review on PR #11733.
abrown commented on PR #11733:
This is not meant to undermine the good work in Sightglass; I actually drop in Sightglass benchmarks to this folder when I want to see how
criterionmeasures things. As we have discussed in prior Cranelift meetings, this would just be a shortcut to the very specific use case of "quickly measure a compilation change."
fitzgen submitted PR review.
fitzgen created PR review comment:
let mut group = c.benchmark_group(scenario.to_string());
fitzgen created PR review comment:
Maybe double check that the file path ends in
.wasmand isn't a directory or whatever?
abrown updated PR #11733.
abrown has enabled auto merge for PR #11733.
abrown merged PR #11733.
Last updated: Dec 06 2025 at 06:05 UTC