-
Notifications
You must be signed in to change notification settings - Fork 286
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
refactor: improve call wasm #508
refactor: improve call wasm #508
Conversation
BENCHMARKS
|
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.
Please revert >=
change, rest of the PR looks fine to me. :)
I checked out your PR locally after seeing some regressions according to our benchmarking CI and unfortunately I can confirm locally that some benchmarks are slightly regressed with those changes. |
@Robbepop I do not see regressions in my local |
Codecov Report
@@ Coverage Diff @@
## master #508 +/- ##
==========================================
- Coverage 79.73% 79.73% -0.01%
==========================================
Files 75 75
Lines 6292 6291 -1
==========================================
- Hits 5017 5016 -1
Misses 1275 1275
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
0c0e4a7
to
7bd3acc
Compare
:( execute/memory_vec_add meet a lot regressions. Why? |
I don't know. Could be an artifact. Unfortunately |
Hi, seems now it at least not make regressions. @Robbepop |
Why is red when improved? Such as 🔴 -3.70% 🔴 -0.35% |
Strange, wasm_kernel is not stable, I see a big improvement last time. |
@Robbepop It now seems is a good improvement that could be merged now. |
The problem with those benchmarks is that they are currently extremely flaky/noisy for this PR in particular. I don't know why that is but we cannot really trust those benchmarks fully with respect to this PR. I will take a look today on it and decide if we want to merge it. |
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.
I checked out benchmarks locally for this PR and it now seems to be fine. LGTM therefore.
- checkrecursion_limit
by>=