From: Erwan Velu <e.velu@criteo.com>
To: Jens Axboe <axboe@kernel.dk>,
Hans-Peter Lehmann <hans-peter.lehmann@kit.edu>,
"fio@vger.kernel.org" <fio@vger.kernel.org>
Subject: Re: Question: t/io_uring performance
Date: Tue, 21 Sep 2021 09:05:56 +0200 [thread overview]
Message-ID: <abf13615-4243-e102-5c1d-cb252c679b1a@criteo.com> (raw)
In-Reply-To: <796c8f29-323a-6fbc-09fc-5c739c81a221@criteo.com>
Le 16/09/2021 à 23:18, Erwan Velu a écrit :
>
> On 09/09/2021 00:37, Erwan Velu wrote:
>> [...]
>> So I made a try !
>>
>>
>> 2 devices on a single physical core brings me up to 1.23M (that's 67%
>> of the previous result on two physical cores)
>>
>> 3 devices on a two physical cores bring me up to 1.85M
>>
>> 4 devices on a two physical cores bring me up to 2.48M
>>
>> 4 devices on a three physical cores bring me up to 3.77M
>>
> To ease the reproducer, I created a script
> https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Faxboe%2Ffio%2Fpull%2F1272&data=04%7C01%7Ce.velu%40criteo.com%7C790c95d308a04c6e9c4308d9795785f5%7C2a35d8fd574d48e3927c8c398e225a01%7C1%7C0%7C637674239079752317%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=vBAwZnAJzkSAag3k6PW2kCDBStrap5rM1joFWuaG6MY%3D&reserved=0
> that automate all this and fixes the usual config mistakes.
>
> Feel free to test it !
Just merged by Jens :
https://github.com/axboe/fio/commit/0c6c0ebb82504da41ff2aa7a382923d9713b40ab
Feel free to use t/one-core-peak.sh to test your setup, feel free to
comment & patch.
Erwan,
next prev parent reply other threads:[~2021-09-21 7:06 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
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 [this message]
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=abf13615-4243-e102-5c1d-cb252c679b1a@criteo.com \
--to=e.velu@criteo.com \
--cc=axboe@kernel.dk \
--cc=fio@vger.kernel.org \
--cc=hans-peter.lehmann@kit.edu \
/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).