-
Notifications
You must be signed in to change notification settings - Fork 30
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
chore: enable WASM support #430
Conversation
🦋 Changeset detectedLatest commit: dec8791 The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Performance Comparison ReportSignificant Changes To Duration
Show details
Meaningless Changes To DurationShow entries
Show details
Changes To CountThere are no entries Added ScenariosThere are no entries Removed ScenariosThere are no entries |
@mdjastrzebski thanks for the fix. Indeed, running node with the options: I also noticed from running Also, I ran some tests with the
To me it seems that adding P.S. I am no expert in reassure so please correct me if I haven't tested this properly! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me! 🎉
🎉 This PR has been released in v0.10.2! |
Summary
This PR adds support for Reassure
--enable-wasm
option that would replace--jitless
flag for--no-opt --no-sparkplug
flags intended to disable Turbo Fan optimizing compiler and Sparkplug non-optimizing compiler in order to maintain execution time stability provided by JIT-less mode.Resolves #426
Resolves #421
Test plan