All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mauricio Tavares <raubvogel@gmail.com>
To: fio <fio@vger.kernel.org>
Subject: Re: CPUs, threads, and speed
Date: Fri, 24 Jan 2020 15:39:18 -0500	[thread overview]
Message-ID: <CAHEKYV4vQ30vSzv7_O4Tzm4S3eFHEA7az91Vrd1dAJXVWuzbMA@mail.gmail.com> (raw)
In-Reply-To: <CAF+0mvmYdsnWj4dPSjeGzrYRgMBh+XFvQxrYB=TGCEDudRiebA@mail.gmail.com>

On Fri, Jan 17, 2020 at 5:08 PM Matthew Eaton <m.eaton82@gmail.com> wrote:
>
> On Thu, Jan 16, 2020 at 11:04 AM Jared Walton <jawalking@gmail.com> wrote:
> >
> > Correct, I pre-condition for IOPS testing by utilizing the the last if
> > block, only using randwrite. which will run random writes for about
> > 45min, until a steady state is achieved.
> >
[...]
>
> I have pretty much standardized on two sequential drive writes and
> four random drive writes to get to steady state. It may be overkill
> but has worked well for me since we test a variety of SSDs and some
> reach steady state faster than others.

Thank you for all the replies and to Jared for the script, which leads
me to one related question: even though it used steady state as
criteria to consider drive preconditioned, am I correct to assume that
steady state does not necessarily have any relationship with the
steady state where I want to take the measurements when actually
running the tests?


  reply	other threads:[~2020-01-24 20:39 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-15 15:50 CPUs, threads, and speed Mauricio Tavares
2020-01-15 17:28 ` Gruher, Joseph R
2020-01-15 18:04   ` Andrey Kuzmin
2020-01-15 18:29     ` Mauricio Tavares
2020-01-15 19:00       ` Andrey Kuzmin
2020-01-15 20:36         ` Mauricio Tavares
2020-01-16  6:59           ` Andrey Kuzmin
2020-01-16 16:12             ` Mauricio Tavares
2020-01-16 17:03               ` Andrey Kuzmin
2020-01-16 17:25               ` Jared Walton
2020-01-16 18:39                 ` Andrey Kuzmin
2020-01-16 19:03                   ` Jared Walton
2020-01-17 22:08                     ` Matthew Eaton
2020-01-24 20:39                       ` Mauricio Tavares [this message]
2020-01-15 18:33   ` Kudryavtsev, Andrey O
2020-01-15 21:33 ` Elliott, Robert (Servers)
2020-01-15 22:39   ` Mauricio Tavares
2020-01-16  0:49     ` Ming Lei

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=CAHEKYV4vQ30vSzv7_O4Tzm4S3eFHEA7az91Vrd1dAJXVWuzbMA@mail.gmail.com \
    --to=raubvogel@gmail.com \
    --cc=fio@vger.kernel.org \
    /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.