Skip to content
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

IOLimitTuner may not work well in a special case #6099

Closed
JinheLin opened this issue Oct 11, 2022 · 0 comments · Fixed by #6098
Closed

IOLimitTuner may not work well in a special case #6099

JinheLin opened this issue Oct 11, 2022 · 0 comments · Fixed by #6098
Assignees
Labels
affects-5.0 affects-5.1 affects-5.2 affects-5.3 affects-5.4 This bug affects the 5.4.x(LTS) versions. affects-6.1 This bug affects the 6.1.x(LTS) versions. component/storage severity/major type/bug The issue is confirmed as a bug.

Comments

@JinheLin
Copy link
Contributor

If both max_bg_read_bytes_per_sec and max_fg_read_bytes_per_sec are less than io_config.min_bytes_per_sec and bg_read runs out of the bandwidth quota, but fg_read has not been used.

The usage rate of read is (max_bg_read_bytes_per_sec + 0 ) / (max_bg_read_bytes_per_sec + max_fg_read_bytes_per_sec), about 50%. It is less than io_config.medium_pct (60% by default), so watermark is LOW.

The LOW watermark means that bandwidth quota of read is sufficient since the usage rate is less than 60%, so it is unnessary to increase its bandwidth quota by decreasing the bandwidth quota of write.

In this case, bg_read will increase its bandwidth quota by decreasing the bandwidth quota of fg_read. However, fg_read is less than io_config.min_bytes_per_sec, it is too small to decrease.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
affects-5.0 affects-5.1 affects-5.2 affects-5.3 affects-5.4 This bug affects the 5.4.x(LTS) versions. affects-6.1 This bug affects the 6.1.x(LTS) versions. component/storage severity/major type/bug The issue is confirmed as a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants