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 15:17:03 +0200 [thread overview]
Message-ID: <74c59a8b-9475-6554-7d93-f9c5f26cc652@criteo.com> (raw)
In-Reply-To: <1b1c961d-ddba-18de-e0ff-fd8cf60f5da8@kit.edu>
Le 01/09/2021 à 12:36, Hans-Peter Lehmann a écrit :
> I couldn't find details about Jens' processor frequency but I would be
> surprised if he had ~3 times the frequency of ours (2.0 GHz base, 3.2
> GHz boost).
Can you check how the processor performance goes during the run ?
This would help ensuring the processors clocks perfectly during your run.
To ease this part, you can use the exec module I committed recently in
fio : https://github.com/axboe/fio/blob/master/examples/exec.fio
There is an example on how dumping the cpuperf in // of a particular
workload.
If you don't want to use this, you can just run the turbostat cmdline
I'm sharing in this example.
Cheers,
Erwan,
next prev parent reply other threads:[~2021-09-01 13:18 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 [this message]
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
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=74c59a8b-9475-6554-7d93-f9c5f26cc652@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.