-
Notifications
You must be signed in to change notification settings - Fork 808
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
Avoid computing rpc_blob_limits multiple times #6595
Conversation
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.
Nice find!
The test failure looks related. It might be because |
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.
nice find! what else showed up in the flamegraph?
Moved rpc_tests to run over MainnetEthSpec. I think it made a difference when minimal blob sizes were small. Don't think it makes much of a difference in terms of test speeds now. Not sure if there's any reason to run them over minimal cc @AgeManning for when you are back |
|
Mostly signature verification and decompression taking up cpu time. Milhouse uses a lot of stack depth. Both are expected I guess. |
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 good.
@mergify queue |
✅ The pull request has been merged automaticallyThe pull request has been merged automatically at 6e1945f |
* Compute blob rpc limits in static block * Fix min size * Use MainnetEthSpec in rpc tests * Revert MainnetEthSpec; add another constant for blob size minimal
Issue Addressed
N/A
Proposed Changes
rpc_blob_limits was being computed repeatedly even though its a constant value. Move it to a LazyLock block to avoid repeated computation.
Found this taking ~10% of cpu when I was playing around with flamegraph