Flexible I/O Tester development
 help / color / mirror / Atom feed
From: Stephen Bates <sbates@raithlin.com>
To: Erwan Velu <e.velu@criteo.com>
Cc: fio@vger.kernel.org, erwanaliasr1@gmail.com,
	Martin.Oliveira@eideticom.com, info@bytehamster.com
Subject: Re: one-core-peak.sh
Date: Fri, 7 Oct 2022 11:33:47 -0600	[thread overview]
Message-ID: <Y0Bi+zovJvCha4Gy@bunbeg> (raw)
In-Reply-To: <9a806c16-ccc4-d31f-e421-87ee93d4fcce@criteo.com>

The 10/07/2022 10:31, Erwan Velu wrote:
> Le 06/10/2022 à 23:00, Stephen Bates a écrit :
> > Hi All
> > 
> > We are working on measuring one core peak performance and have been
> > using the one-core-peak.sh script. While the script does what it needs
> > to do we find it a bit hard to use and not written in an ideal
> > fashion. We are planning to do a python version which can be done in a
> > much cleaner and more readable fashion.
> > 
> > Rather than stomping on toes and just sending a patch to replace this
> > script I wanted to solicit feedback from the original authors and
> > community that this is acceptable.
> 
> Hey,
> 
> Thanks for reaching out.
> 
> I wrote this tool as a simple helper and though it would be short enough to
> stay in bash.
> 
> The bash was clearly a POC more than a solution.
> 
> I totally support moving to python3. I can provide help in this.
> 
> Erwan,
>

Hi Erwan

Thanks for responding! I have opened an issue on Jen's GitHub repo [1]. If you or anyone else fancy collaborating on this please reach out to me. We can work on my fork of fio [2] if it suits and then prepare a patchset.

-- 

Cheers

Stephen

[1]: https://github.com/axboe/fio/issues/1476
[2]: https://github.com/sbates130272/fio

      reply	other threads:[~2022-10-07 17:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-06 21:00 one-core-peak.sh Stephen Bates
2022-10-07  8:31 ` one-core-peak.sh Erwan Velu
2022-10-07 17:33   ` 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=Y0Bi+zovJvCha4Gy@bunbeg \
    --to=sbates@raithlin.com \
    --cc=Martin.Oliveira@eideticom.com \
    --cc=e.velu@criteo.com \
    --cc=erwanaliasr1@gmail.com \
    --cc=fio@vger.kernel.org \
    --cc=info@bytehamster.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox