-
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
Add #[inline] annotations to small functions in wasmi_core crate #348
Conversation
I don't see a clear win in the first benchmarks you posted (the first box). Some regressed and some improved. I think using profile guided optimization would be a more systematic approach. |
Yeah I will explain. In the benchmarks most |
We shouldn't merge it then, right? Cause we are actually still using |
I currently do not plan to release another
|
Note that I have only benchmarked |
I don't care about other profiles which are clearly inferior. We shouldn't just merge inlines on a hunch when they even pessimise the profile and version of the crate we are currently using (or will be using very soon). |
I guess this PR then has to wait until |
@athei can I merge this since we no longer really seem to be interested in merging any of the old |
Yeah sure. |
This PR is a refinement of this PR.
The main difference between this PR and the former is that I only annotated relevant functions in the
wasmi_core
crate.I verified with benchmarks that the best case performance is not regressed.
In fact benchmarks show some neat wins in performance even in the current best case profile settings.
Compared to the original PR there are fewer gains on the default release profile: