-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ensure that the handling for the V128_BITCAST APIs is correctly performant on Mono WASM #105009
Conversation
…rmant on Mono WASM
Tagging subscribers to this area: @BrzVlad, @kotlarmilos |
The MOV_VT numbers are very promising! Thanks for chasing this down. |
This should be ready for review, CI failures are flaky tests hitting OOM/timeouts and I'm rerunning them |
@tannergooding thanks for getting this done so quickly, the initial data from our benchmarks also indicate there now a net improvement in here. Excellent work. |
@mkhamoyan can you please update the documentation in dotnet/performance |
Glad I was finally able to figure it out, hopefully it should make future improvements easier as well 😄 |
Only gave a single example below, but did run a sampling of benchmarks and the results look to be correct now.
Notably the docs for running WASM benchmarks is very out of date right now: https://github.com/dotnet/performance/blob/main/docs/benchmarking-workflow-dotnet-runtime.md#dotnet-runtime-testing-for-wasm, I ended up getting it working but having up to date guidance would be great.
-- Most notably
test-main.js
was moved, tests won't run since it can't find the9.0.0-dev
packages, andtest-main.js
was updated to require--module
This should resolve dotnet/perf-autofiling-issues#38466
Interpreter
No Handling
V128_BITCAST Handling
MOV_VT Handling
AOT
No Handling
V128_BITCAST Handling
MOV_VT Handling