-
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
[Builtins] Update 'BuiltinRuntime' to store the costing function strictly #4496
Conversation
/benchmark plutus-benchmark:validation |
Comparing benchmark results of 'plutus-benchmark:validation' on '4c619351b' (base) and 'c8351e0fb' (PR)
|
-2.59% on average. Some free speedup right there. Thanks to @bezirg for bringing it up. |
The tests that run the CK machine fail now. |
Speedup looks good, though! |
Ah, I forgot that it wasn't doing any costing too. I'll do something about it, perhaps introduce some kind of dummy costing or whatever. |
c8351e0
to
136cd3c
Compare
Done. |
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 fine.
FYI I've got an issue to store actual functions for costing, rather than objects containing parameters that have to be looked up an used to calculate the cost every time (I assume) that the costing function is called. I keep getting distracted from that though. |
I was going to look into that too. Let me first try to optimize the existing stuff, maybe it's fine to have objects containing parameters as long as we don't need to match on them every time. |
Since the HOAS evaluator is gone, we don't need that laziness anymore.