-
Notifications
You must be signed in to change notification settings - Fork 483
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
Remove caching of builtin runtimes #4319
Conversation
…to effectfully/evaluation/no-lookup-builtin-2
/benchmark |
This reverts commit c016cff.
Comparing benchmark results of '4710dff2e' (base) and 'c016cff89' (PR)
|
Nice :) |
This reverts commit f8879b6.
/benchmark |
Comparing benchmark results of '4710dff2e' (base) and '90dded294' (PR)
|
/benchmark |
Comparing benchmark results of '4710dff2e' (base) and '250ae7ba4' (PR)
|
Well, that is surprising to me. The code now is supposed to push all the thunks for meanings of builtins outside if the main loop, so that they're only created once, but either I've failed at that (I should try using some |
Ok, I'm pretty clueless as to what's going on here. The thing is, we might be having the same problem at startup currently without knowing it. Whatever is slow here is quite likely also slow during the initial traversal where we compute the |
That's true. However, if that's the case we can certainly address it on the ledger side by ensuring that that is only done once and is then cached. |
Don't look here yet.