From: Matthew Eaton <m.eaton82@gmail.com>
To: fio@vger.kernel.org
Subject: high cpu usage when replaying iolog
Date: Thu, 22 Feb 2024 12:15:52 -0800 [thread overview]
Message-ID: <CAF+0mvmpbx+tcfrH7gz0paXhwg9WVGtD96NS68_2_WsXNKgC3w@mail.gmail.com> (raw)
Using fio 3.36 and the latest fio from git I noticed high cpu usage
when replaying iolog:
fio --name=replay --ioengine=io_uring --direct=1 --iodepth=1
--read_iolog=test.iolog --replay_redirect=/dev/nvme0n1
cpu : usr=50.27%, sys=33.79%, ctx=45686, majf=0, minf=11
When I revert this commit the cpu usage goes back to normal:
https://git.kernel.dk/cgit/fio/commit/?id=b85c01f7e9dfc468eb78faf86692433e6105178d
cpu : usr=0.23%, sys=0.56%, ctx=219444, majf=0, minf=11
Is this a bug or expected?
next reply other threads:[~2024-02-22 20:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-22 20:15 Matthew Eaton [this message]
2024-02-23 15:34 ` high cpu usage when replaying iolog Vincent Fu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAF+0mvmpbx+tcfrH7gz0paXhwg9WVGtD96NS68_2_WsXNKgC3w@mail.gmail.com \
--to=m.eaton82@gmail.com \
--cc=fio@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).