From: Daniel Menzel <daniel.menzel@menzel-it.net>
To: Jens Axboe <axboe@kernel.dk>,
"Ober, Frank" <frank.ober@intel.com>,
"fio@vger.kernel.org" <fio@vger.kernel.org>
Subject: Re: io_uring on CentOS8?
Date: Wed, 17 Feb 2021 09:42:40 +0100 [thread overview]
Message-ID: <0fa8b1c4-ccdf-7f75-7962-c97e55153707@menzel-it.net> (raw)
In-Reply-To: <c115f8ee-a466-8225-99e9-765384bb2ba2@kernel.dk>
By the way: Does anyone do some system profiling (flame graphs or
something like that) while testing devices to make sure you reached the
devices' capabilities instead of the systems?
I just made some tests of nvme drives and a friend of mine (who is a
scientist) said that if that was a paper he would reject it because I do
not know whether I measure the devices or the system.
Am 16.02.21 um 20:51 schrieb Jens Axboe:
> On 2/16/21 12:00 PM, Ober, Frank wrote:
>> Hi Daniel, Intel uses pvsync2 for QD1 testing so if you cannot use spdk or io_uring (these are the fastest ways to test a device), you can switch your engine to pvsync2 on this kernel and this will work.
>>
>> Here's what I tried on PCIe Gen3 system with an Optane drive and your drive.
>>
>>
>> [root@fm42adsdemo001 block]# fio --bs=1M --rw=randwrite --numjobs=1 --iodepth=1 --size=10000M \
>>> --filename=/dev/nvme6n1 --name=mylittletest --direct=1 --fsync=1 \
>>> --refill_buffers --ioengine=pvsync2 --group_reporting \
>>> --fallocate=none --runtime=60 --time_based --hipri
>> mylittletest: (g=0): rw=randwrite, bs=(R) 1024KiB-1024KiB, (W) 1024KiB-1024KiB, (T) 1024KiB-1024KiB, ioengine=pvsync2, iodepth=1
>> fio-3.24-5-g2ee2
>> Starting 1 process
>> Jobs: 1 (f=1): [w(1)][100.0%][w=2048MiB/s][w=2048 IOPS][eta 00m:00s]
>>
>> I ran the same exact job on this mid-range Intel Xeon cpu and found io_uring only very slightly faster than pvsync2
>> Jobs: 1 (f=1): [w(1)][100.0%][w=2057MiB/s][w=2057 IOPS][eta 00m:00s]
> That's not too surprising, if you're at queuedepth=1 or doing sync IO, then
> I'd consider it a major win that the async API is just as fast or faster
> than the sync one :-)
>
>
--
Daniel Menzel
Geschäftsführer
Menzel IT GmbH
Charlottenburger Str. 33a
13086 Berlin
+49 (0) 30 / 5130 444 - 00
daniel.menzel@menzel-it.net
https://menzel-it.net
Geschäftsführer: Daniel Menzel, Josefin Menzel
Unternehmenssitz: Berlin
Handelsregister: Amtsgericht Charlottenburg
Handelsregister-Nummer: HRB 149835 B
USt-ID: DE 309 226 751
prev parent reply other threads:[~2021-02-17 8:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-14 15:17 io_uring on CentOS8? Daniel Menzel
2021-02-14 16:49 ` Jens Axboe
2021-02-16 19:00 ` Ober, Frank
2021-02-16 19:46 ` Daniel Menzel
2021-02-16 19:51 ` Jens Axboe
2021-02-17 8:42 ` Daniel Menzel [this message]
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=0fa8b1c4-ccdf-7f75-7962-c97e55153707@menzel-it.net \
--to=daniel.menzel@menzel-it.net \
--cc=axboe@kernel.dk \
--cc=fio@vger.kernel.org \
--cc=frank.ober@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.