-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Relocation of memory.grow and memory.size #199
Comments
Oooh I do like the idea of having a command line argument which would allow the user to choose between a fast startup but poorer performance, and better performance but slower startup. So a definite +1 for that from me :-) |
I wonder if this requires dedicated flags or it could be generalized as, bikeshedingly, |
Thes relocations ended up getting removed in #949 and we can always make a new issue if the current relocation strategy is too slow for some use cases! |
Adjust SHA256 benchmark code
As we discussed with @sunfishcode, after merging #194 there's probably no need for
{Imported,}Memory32{Grow,Size}
in RelocationTarget, or at least the tests pass. However, there are is an idea for having a command line setting which allows user to choose between fast startup using cache and less relocations, or better performance paying extra time for compilation and relocation. The mentioned code hasn't been deleted and it's just a tracking issue.The text was updated successfully, but these errors were encountered: