Skip to content

Conversation

@posborne
Copy link
Collaborator

You can now, for example, do the following to capture timing, cycles, and perf-counters data on a single run...

cargo run -- benchmark \
    --engine engines/wasmtime/libengine.dylib \
    --raw -o result.json \
    -m time -m cycles -m perf-counters \
    -- benchmarks/all.suite

While imperfect, this is still useful data that anchors benchmark
iterations to a number that is more meaningful to humans sometimes.
Combined with the ability to capture multiple measures, this is
pretty useful to have available.
Previously, only a single measure type could be requested.  Often,
we might want to capture multiple measures on a benchmark run as
different measurements might provide a more complete picture of
a given benchmark iteration.
@posborne posborne force-pushed the support-multiple-benchmark-measures branch from 8fd0df4 to 6e8357d Compare April 17, 2025 20:35
Copy link
Member

@abrown abrown left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@abrown abrown merged commit f5b9683 into bytecodealliance:main Apr 21, 2025
17 checks passed
posborne added a commit to posborne/sightglass that referenced this pull request Apr 28, 2025
* Add simple time measurement

While imperfect, this is still useful data that anchors benchmark
iterations to a number that is more meaningful to humans sometimes.
Combined with the ability to capture multiple measures, this is
pretty useful to have available.

* Add support for capturing multiple measurements

Previously, only a single measure type could be requested.  Often,
we might want to capture multiple measures on a benchmark run as
different measurements might provide a more complete picture of
a given benchmark iteration.
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.

2 participants