-
Notifications
You must be signed in to change notification settings - Fork 598
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
refactor(dashboard): refactor back-pressure calculation #19954
Conversation
This stack of pull requests is managed by Graphite. Learn more about stacking. |
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.
Most LGTM
return () => { | ||
clearInterval(interval) | ||
} | ||
}, [toast, resetEmbeddedBackPressures]) | ||
|
||
// Get relationId-relationId -> backpressure rate map | ||
// Convert fragment-level backpressure rate map to relation-level backpressure rate |
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.
QQ: what is relation-level backpressure rate?
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.
E.g. backpressure between MVs
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 hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
Based on the previous PR, this PR rewrite the back-pressure calculation code in much less code.
I did this because I am going to add more statistics to the Web dashboard, such as streaming throughput.
Checklist
Documentation
Release note