-
Notifications
You must be signed in to change notification settings - Fork 5.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
Release Performance Regression 2.3.0/2.3.1 #33187
Conversation
Signed-off-by: Cindy Zhang <[email protected]>
"large_object_size": 107374182400, | ||
"large_object_time": 325.56598805499993, | ||
"large_object_time": 490.7879660510001, |
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.
is this expected?
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.
what are the PRs we have cherry picked since 2.3.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.
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 think this is the one with very high variance on the V1 stack due to EBS. I think we should run it again to be sure that it's a regression and not just network tail latency.
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.
Synced with @rickyyx @cadedaniel, the metrics difference is believed to just be the expected variance. Kicked off a rerun of tests single_node
and microbenchmark
here and here so that we can be more confident in this hypothesis. @scv119
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.
thanks @zcin, yeah let's retry here!
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.
Output from compare_perf_metrics: https://docs.google.com/spreadsheets/d/1lSCLAQ7ghc4uOk80L3e9S2Rxuy7a2d3nbJRPi9D7brM/edit#gid=0 Signed-off-by: Jack He <[email protected]>
Output from compare_perf_metrics: https://docs.google.com/spreadsheets/d/1lSCLAQ7ghc4uOk80L3e9S2Rxuy7a2d3nbJRPi9D7brM/edit#gid=0 Signed-off-by: Edward Oakes <[email protected]>
Output from compare_perf_metrics: https://docs.google.com/spreadsheets/d/1lSCLAQ7ghc4uOk80L3e9S2Rxuy7a2d3nbJRPi9D7brM/edit#gid=0 Signed-off-by: chaowang <[email protected]>
Output from compare_perf_metrics: https://docs.google.com/spreadsheets/d/1lSCLAQ7ghc4uOk80L3e9S2Rxuy7a2d3nbJRPi9D7brM/edit#gid=0 Signed-off-by: elliottower <[email protected]>
Output from compare_perf_metrics: https://docs.google.com/spreadsheets/d/1lSCLAQ7ghc4uOk80L3e9S2Rxuy7a2d3nbJRPi9D7brM/edit#gid=0 Signed-off-by: Jack He <[email protected]>
Why are these changes needed?
Output from
compare_perf_metrics
:https://docs.google.com/spreadsheets/d/1lSCLAQ7ghc4uOk80L3e9S2Rxuy7a2d3nbJRPi9D7brM/edit#gid=0
Related issue number
Checks
git commit -s
) in this PR.scripts/format.sh
to lint the changes in this PR.