From: Stephen Bates <sbates@raithlin.com>
To: Vincent Fu <vincentfu@gmail.com>
Cc: fio@vger.kernel.org
Subject: Re: Project to standardize on IOPS per CPU core
Date: Tue, 20 Sep 2022 18:05:31 -0600 [thread overview]
Message-ID: <YypVS3B8oegOecd5@bunbeg> (raw)
In-Reply-To: <0ba23bde-1b80-414d-c520-ab39687bf892@gmail.com>
The 09/20/2022 17:47, Vincent Fu wrote:
> On 9/20/22 14:08, Stephen Bates wrote:
> > Hi fio'ers
> >
> > I have been working with a few others on NVMe performance in a range
> > of different environments. At the same time I have been tracking some
> > of the reports on IOPS per core for NVMe+io_uring [1][2]. I was hoping
> > to create a standrd and repeatable test for this using a mix of
> > packer, Ansible and AWS machines.
> >
> > The idea would be a scriptable flow to obtain a working
> > fio+libiouring+kernel on some AWS EC2 instance(s) and then automate
> > some tests to obtain IOPS per CPU core.
> >
> > To help me get started on this does anyone have any pointers on how
> > best to configure the system to maximize this metric? Also any fio
> > scripts for this that people can point me too would be excellent.
> >
> > If there is interest I would happily work this into a patch for fio
> > (perhaps in some sort of CI way).
> >
> > Cheers
> >
> > Stephen Bates, PhD.
> >
> > [1]: https://www.phoronix.com/news/7.4M-IOPS-Linux-Per-Core
> > [2]: https://twitter.com/axboe/status/1452689372395053062?lang=en
>
> Stephen, t/one-core-peak.sh was added last year by Erwan Velu and might be
> useful to you:
>
> https://github.com/axboe/fio/blob/master/t/one-core-peak.sh
>
> Vincent
Vincent
Oh thanks! This is great. I will take a look at this and go from there.
--
Cheers
Stephen Bates, PhD.
prev parent reply other threads:[~2022-09-21 0:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-20 18:08 Project to standardize on IOPS per CPU core Stephen Bates
2022-09-20 21:47 ` Vincent Fu
2022-09-21 0:05 ` Stephen Bates [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=YypVS3B8oegOecd5@bunbeg \
--to=sbates@raithlin.com \
--cc=fio@vger.kernel.org \
--cc=vincentfu@gmail.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.