Skip to content

Adjust pca.R to choose a cluster representative closest to 100M Wasm instructions executed#322

Merged
cfallin merged 1 commit into
bytecodealliance:mainfrom
fitzgen:adjust-pca-script-to-aim-for-100M-wasm-insts
Jun 25, 2026
Merged

Adjust pca.R to choose a cluster representative closest to 100M Wasm instructions executed#322
cfallin merged 1 commit into
bytecodealliance:mainfrom
fitzgen:adjust-pca-script-to-aim-for-100M-wasm-insts

Conversation

@fitzgen

@fitzgen fitzgen commented Jun 25, 2026

Copy link
Copy Markdown
Member

Rather than the fewest Wasm instructions executed. 100M was chosen previously as a large enough number to avoid lots of noise and to fill our callgrind-simulated caches, but small enough to run individual iterations relatively quickly.

…m instructions executed

Rather than the fewest Wasm instructions executed. 100M was chosen previously as
a large enough number to avoid lots of noise and to fill our callgrind-simulated
caches, but small enough to run individual iterations relatively quickly.
@fitzgen fitzgen requested a review from cfallin June 25, 2026 19:35
@cfallin cfallin merged commit f603377 into bytecodealliance:main Jun 25, 2026
12 checks passed
@cfallin

cfallin commented Jun 25, 2026

Copy link
Copy Markdown
Member

Ah, oops, this repo doesn't have a test-gated merge like Wasmtime does -- I clicked 'merge' expecting it would do so after tests passed. If they don't, now, happy to review followups; sorry about that...

@fitzgen fitzgen deleted the adjust-pca-script-to-aim-for-100M-wasm-insts branch June 25, 2026 21:50
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