From: Hans-Peter Lehmann <hans-peter.lehmann@kit.edu>
To: Erwan Velu <e.velu@criteo.com>,
"fio@vger.kernel.org" <fio@vger.kernel.org>
Subject: Re: Question: t/io_uring performance
Date: Mon, 6 Sep 2021 16:26:21 +0200 [thread overview]
Message-ID: <77b67cc0-30c1-70a8-438b-f1bcf1fdb295@kit.edu> (raw)
In-Reply-To: <e41a49a8-f5ea-9f50-0327-dd2af9487153@criteo.com>
Hi Jens,
not sure if you have read the emails in this thread - now trying to address you directly. Both Erwan and me are unable to reproduce your single-threaded IOPS measurements - we don't even get close to your numbers. The bottle-neck seems to be the CPU, not the SSDs. Did you use some special configuration for your benchmarks?
Best regards
Hans-Peter
(I have also reproduced the behavior with an Intel processor now - the single-threaded throughput is also capped at around 580k IOPS, even though the SSDs can handle more than that when using multiple threads)
next prev parent reply other threads:[~2021-09-06 14:26 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-25 15:57 Question: t/io_uring performance Hans-Peter Lehmann
2021-08-26 7:27 ` Erwan Velu
2021-08-26 15:57 ` Hans-Peter Lehmann
2021-08-27 7:20 ` Erwan Velu
2021-09-01 10:36 ` Hans-Peter Lehmann
2021-09-01 13:17 ` Erwan Velu
2021-09-01 14:02 ` Hans-Peter Lehmann
2021-09-01 14:05 ` Erwan Velu
2021-09-01 14:17 ` Erwan Velu
2021-09-06 14:26 ` Hans-Peter Lehmann [this message]
2021-09-06 14:41 ` Erwan Velu
2021-09-08 11:53 ` Sitsofe Wheeler
2021-09-08 12:22 ` Jens Axboe
2021-09-08 12:41 ` Jens Axboe
2021-09-08 16:12 ` Hans-Peter Lehmann
2021-09-08 16:20 ` Jens Axboe
2021-09-08 21:24 ` Hans-Peter Lehmann
2021-09-08 21:34 ` Jens Axboe
2021-09-10 11:25 ` Hans-Peter Lehmann
2021-09-10 11:45 ` Erwan Velu
2021-09-08 12:33 ` Jens Axboe
2021-09-08 17:11 ` Erwan Velu
2021-09-08 22:37 ` Erwan Velu
2021-09-16 21:18 ` Erwan Velu
2021-09-21 7:05 ` Erwan Velu
2021-09-22 14:45 ` Hans-Peter Lehmann
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=77b67cc0-30c1-70a8-438b-f1bcf1fdb295@kit.edu \
--to=hans-peter.lehmann@kit.edu \
--cc=e.velu@criteo.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 NNTP newsgroup(s).