-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
[Optimize] Further blocking tweaks #3148
[Optimize] Further blocking tweaks #3148
Conversation
@vicsn @onetrickwolf @iamalwaysuncomfortable We will need to validate this branch with at least 12 hours of burn-in prior to approvals. |
I'll fix the |
…rker Signed-off-by: ljedrz <ljedrz@gmail.com>
Signed-off-by: ljedrz <ljedrz@gmail.com>
0dfccdb
to
b1b3485
Compare
Double-clicking on this. @vicsn @onetrickwolf @iamalwaysuncomfortable Did we get a chance to burn-in test this change? |
@vicsn @onetrickwolf @iamalwaysuncomfortable When will this be addressed? |
Starting to test this now |
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.
LGTM, adding this in for additional burn-in testing overnight.
Looks good. Ran for 12+ hours with 1.6 TPS and 3 seconds/block. |
This PR moves 2 additional potentially blocking operations into blocking tasks; they were found to be significant using
tokio-console
, which was also used to double-check that these changes decrease theBusy
time of the associated tasks.