New parameter for max concurrent seals #192
Merged
Conversation
This file contains 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
ZanCorDX
requested review from
dvush,
ferranbt,
metachris and
jakubhruby7
as code owners
dvush
approved these changes
Sep 26, 2024
Benchmark results for
|
| Date (UTC) | 2024-09-26T14:33:42+00:00 |
| Commit | 6eb7f5fbd7358d7ee4faaff7c5205d5947ef745f |
| Base SHA | 00602cc9b97173000afcf78047a72667a3a67cb1 |
Significant changes
| Benchmark | Mean | Status |
|---|---|---|
| MEV-Boost SubmitBlock serialization/JSON encoding | 57.47% | Performance has degraded. |
astarinmymind
pushed a commit
that referenced
this pull request
Oct 3, 2024
## 📝 Summary Adds max_concurrent_seals to the cfg. 1 -> uses SequentialSealerBidMaker >1 -> uses ParallelSealerBidMaker(max_concurrent_seals) ## 💡 Motivation and Context Needed to polish the optimal cfg for the new roothash algo. --- ## ✅ I have completed the following steps: * [x] Run `make lint` * [x] Run `make test` * [ ] Added tests (if applicable)
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.
📝 Summary
Adds max_concurrent_seals to the cfg.
1 -> uses SequentialSealerBidMaker
💡 Motivation and Context
Needed to polish the optimal cfg for the new roothash algo.
✅ I have completed the following steps:
make lintmake test