-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Low hanging fruit in interpreter #1886
Conversation
|
Got it down to:
And for reference, the same benchmark without interpreter runs about the same speed as the first timing above:
|
I'm pretty happy with this but I'll take another look next week before merging. This benchmark doesn't exercise lazy-related stuff (except checking |
I added a memory benchmark too, and the results look ... interesting. Less memory, but more objects: Interpreter
previous
Since it's mostly I'll have to look next week |
Ok, I couldn't just sleep on it, I got the memory consumption down to less-than-half of the current execution:
|
|
I don't want to fuss over this too much, because the application benchmarks might be different from isolated ones, but I thought I'd look for low-hanging fruit now.
I added a benchmark based on #861, here's the initial result:
Method calls