-
Notifications
You must be signed in to change notification settings - Fork 1.6k
feat: add config for reserved CPU cores Resolves paradigmxyz/reth#15633 #15710
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
feat: add config for reserved CPU cores Resolves paradigmxyz/reth#15633 #15710
Conversation
You can put this is in the PR description instead of the title btw (Just a passing comment, have not checked the PR) |
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.
makes sense, ty.
smol nits
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.
ty,
I changed the arg to usize, which makes this easier to use
…aradigmxyz#15710) Co-authored-by: Matthias Seitz <[email protected]>
Dear cores,
This is my first PR! Thanks for your time in reviewing and I will be happy to do any further optimization for this little adding.
I also noticed that RPC server also has a fixed number 2 for reserving CPU cores.
reth/crates/rpc/rpc-server-types/src/constants.rs
Line 26 in 5a1cdfd
As per my user experience, the Sender Recovery stage was the only one with performance issue when there were a lot of syncing to do. The best way to prevent any performance concern should be adding a global configuration for the reserved CPU cores. However, in respect to the modular design, I decided not to touch the RPC part as it had never ate too much CPU.