Skip to content
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

Cache compiled native code produced from wasm modules #524

Open
kazimuth opened this issue Nov 3, 2023 · 1 comment
Open

Cache compiled native code produced from wasm modules #524

kazimuth opened this issue Nov 3, 2023 · 1 comment

Comments

@kazimuth
Copy link
Contributor

kazimuth commented Nov 3, 2023

The main reason I'm interested in this is that it could speed up benchmarks run under callgrind by a lot. Note that it's possible to compile wasm modules while running callgrind, just quite slow.

This should probably wait until after we validate + merge wasmtime (since callgrind doesn't play nice with wasmer, but likes wasmtime.)

@kulakowski
Copy link
Contributor

Is the idea to compile fast not under callgrind, stash the native code, and have a benchmark use that stashed version?

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

No branches or pull requests

2 participants