All of lore.kernel.org
 help / color / mirror / Atom feed
From: Erwan Velu <e.velu@criteo.com>
To: Hans-Peter Lehmann <hans-peter.lehmann@kit.edu>,
	"fio@vger.kernel.org" <fio@vger.kernel.org>
Subject: Re: Question: t/io_uring performance
Date: Wed, 1 Sep 2021 16:05:49 +0200	[thread overview]
Message-ID: <5015f1e3-eaeb-ef9e-e530-83c21db5aeb7@criteo.com> (raw)
In-Reply-To: <2df22c68-6040-298e-4512-752cd10b7201@kit.edu>


Le 01/09/2021 à 16:02, Hans-Peter Lehmann a écrit :
>> Can you check how the processor performance goes during the run ?
>
> I just executed turbostat manually, like it was in your config file. 
> Looks like the processor performance works as expected - the output 
> clearly shows the point where I started/stopped a single-threaded 
> t/io_uring run. The machine has 128 cores, so a Busy% of 0.78 is 
> exactly one core.
>
> # turbostat -c package -qS --interval 5 -s 
> Busy%,Bzy_MHz,Avg_MHz,CorWatt,PkgWatt,RAMWatt,PkgTmp
> Avg_MHz Busy%   Bzy_MHz CorWatt PkgWatt
> 0       0.01    1500    0.01    68.91
> 0       0.01    1641    0.01    68.90
> 0       0.01    1621    0.01    68.91
> 0       0.03    1561    0.03    68.91
> 0       0.03    1547    0.02    68.93
> 0       0.01    1500    0.01    68.91
> 0       0.01    1657    0.01    68.89
> 26      0.78    3322    3.58    74.58
> 26      0.79    3328    3.63    74.72
> 26      0.79    3331    3.63    74.79
> 26      0.79    3321    3.66    74.87
> 26      0.79    3329    3.64    74.88
> 26      0.79    3328    3.65    74.92
> 26      0.79    3334    3.62    74.92
> 26      0.79    3329    3.62    74.94
> 23      0.69    3331    3.17    74.25
> 0       0.01    1664    0.00    69.12
> 0       0.01    1501    0.01    69.12
> 0       0.02    1566    0.01    69.10
> 0       0.00    1499    0.00    69.07
> 1       0.06    1558    0.04    69.10
>

These numbers are perfect.

I rebuild fio on a 5.4 kernel on a high-end nvme which is 1M iops read 
capable and got stuck at the same number as you aka 580K iops.

So, I'd agree with you something is curious here.



  reply	other threads:[~2021-09-01 14: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 [this message]
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
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=5015f1e3-eaeb-ef9e-e530-83c21db5aeb7@criteo.com \
    --to=e.velu@criteo.com \
    --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 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.