-
Notifications
You must be signed in to change notification settings - Fork 477
feat(tools): benchmarking script for verifying validators resources #6038
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
Merged
+736
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
rach-id
commented
Oct 16, 2025
tools/cpu_requirements/main.go
Outdated
|
||
// Reference times in milliseconds (to be filled with actual values) | ||
const ( | ||
referencePrepareProposalMs = 0.0 |
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.
I'll fill these later
I'll go mod tidy it afterwards |
The output of the tool:
|
evan-forbes
approved these changes
Oct 17, 2025
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.
lfg
=== CPU Specifications ===
Number of Cores: 8
Number of Threads: 16
Clock Speed: 4466.147 MHz
GFNI Support: true
SHA-NI Support: true
==========================
Benchmarking complete!
=== Performance Test Results (128MB/6s Compatibility) ===
Prepare Proposal:
Your time: 295 ms
Reference time: 700 ms
Status: FASTER than reference (2.4x faster)
Process Proposal:
Your time: 397 ms
Reference time: 700 ms
Status: FASTER than reference (1.8x faster)
Finalize Block:
Your time: 111 ms
Reference time: 400 ms
Status: FASTER than reference (3.6x faster)
Propose Block:
Your time: 229 ms
Reference time: 400 ms
Status: FASTER than reference (1.7x faster)
Encode Block:
Your time: 125 ms
Reference time: 400 ms
Status: FASTER than reference (3.2x faster)
Decode Block:
Your time: 345 ms
Reference time: 500 ms
Status: FASTER than reference (1.4x faster)
=== Final Assessment ===
CONGRATULATIONS! Your system is ready for the 128MB/6s upgrade.
Your hardware meets the performance requirements for handling 128MB blocks every 6 seconds.
================================
Done
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
A simple tool to run the computation heavy steps we have that require validators to have fancy hardware, then decide whether their hardware is good or not.
The code is vibe coded, doesn't need to be maintainable. If reviewers disagree, I can polish it.