-
Notifications
You must be signed in to change notification settings - Fork 106
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: adding support to io.weight setting #494
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #494 +/- ##
==========================================
- Coverage 55.67% 55.05% -0.63%
==========================================
Files 552 513 -39
Lines 59419 56761 -2658
==========================================
- Hits 33083 31250 -1833
+ Misses 22899 22181 -718
+ Partials 3437 3330 -107
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
8e58e9d
to
0cd6e00
Compare
Signed-off-by: Robin Lu <robin.lu@bytedance.com>
Signed-off-by: Jianyu Sun <sjycsfldf@gmail.com> Signed-off-by: Robin Lu <robin.lu@bytedance.com>
* feat: adding support to qos level io.weight setting Signed-off-by: Robin Lu <robin.lu@bytedance.com> * feat: adding support to cgroup level io.weight setting Signed-off-by: Jianyu Sun <sjycsfldf@gmail.com> Signed-off-by: Robin Lu <robin.lu@bytedance.com> --------- Signed-off-by: Robin Lu <robin.lu@bytedance.com> Signed-off-by: Jianyu Sun <sjycsfldf@gmail.com>
* feat: adding support to qos level io.weight setting Signed-off-by: Robin Lu <robin.lu@bytedance.com> * feat: adding support to cgroup level io.weight setting Signed-off-by: Jianyu Sun <sjycsfldf@gmail.com> Signed-off-by: Robin Lu <robin.lu@bytedance.com> --------- Signed-off-by: Robin Lu <robin.lu@bytedance.com> Signed-off-by: Jianyu Sun <sjycsfldf@gmail.com>
What type of PR is this?
Features
What this PR does / why we need it:
This patch provied the feature of io.weight setting.
Which issue(s) this PR fixes:
In production area, some critical services and online pods were affected by busy io.
Special notes for your reviewer:
None.