Skip to content

block: Observing higher CPU utilization during random IO testing#928

Open
blktests-ci[bot] wants to merge 1 commit into
linus-master_basefrom
series/1106086=>linus-master
Open

block: Observing higher CPU utilization during random IO testing#928
blktests-ci[bot] wants to merge 1 commit into
linus-master_basefrom
series/1106086=>linus-master

Conversation

@blktests-ci
Copy link
Copy Markdown

@blktests-ci blktests-ci Bot commented Jun 4, 2026

Pull request for series with
subject: block: Observing higher CPU utilization during random IO testing
version: 1
url: https://patchwork.kernel.org/project/linux-block/list/?series=1106086

Hi All,

Our performance team observed the higher CPU utilization in RHEL10 compared
to RHEL9.8, observed the similar issue in upstream kernel(v7.1-rc6) as well
when running FIO random IO tests. Random IO tests are more CPU intensive
than sequential IO tests due to several factors: more context switching,
interrupt Handling, cache Inefficiency etc.

Given commit 060406c ("block: add plug while submitting IO")
causes performance regression. This patch reverts it.

Below is performance comparison with the latest upstream kernel.

Iotype  qd   nj    rmix    mpstat busy        mpstat busy
                         with inner plug    without inner plug
Randrw  1    20    100       53%                 24%
Randrw  1    40    100       70%                 24%
Randrw  1    20    70        40%                 24%
Randrw  1    40    70        60%                 26%
Randrw  1    20    0         14%                 6%
Randrw  1    40    0         20%                 7%

Signed-off-by: Wen Xiong <wenxiong@linux.ibm.com>
Suggested-by: Ming Lei <tom.leiming@gmail.com>
@blktests-ci
Copy link
Copy Markdown
Author

blktests-ci Bot commented Jun 4, 2026

Upstream branch: ba3e43a
series: https://patchwork.kernel.org/project/linux-block/list/?series=1106086
version: 1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant