From: David Nellans <david@nellans.org>
To: "Brian L." <brianclam@gmail.com>,
"fio@vger.kernel.org" <fio@vger.kernel.org>
Subject: Re: precondition ssd drives w/ fio
Date: Thu, 03 Oct 2013 15:06:01 -0500 [thread overview]
Message-ID: <524DCE29.3050808@nellans.org> (raw)
In-Reply-To: <CAAAK+WW66DdYt2JEG+2K42vWzczn38xtnh5WK-1x97zFbdkyqg@mail.gmail.com>
On 10/03/2013 02:31 PM, Brian L. wrote:
> For benchmarking SSD drives, I was told that we should precondition
> our drives to get more accurate real world reading.
>
> I was wondering if anyone is using fio itself to precondition ssd
> drives or use a different script to populate random data on the
> drives?
>
> Thanks in advance.
>
> Brian L.
> --
> To unsubscribe from this list: send the line "unsubscribe fio" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
fio is flexible enough that it can precondition with just about any
shape of traffic you're willing to craft a job for. but what traffic
you believe is representative of your real world use case
is entirely up to you and can have dramatic affect on the garbage
collection efficiency of the drive.
google "ssd preconditioning" and many of the flash manufacturers have
whitepapers on how/why you might choose to precondition your drives
before doing any benchmarking.
next prev parent reply other threads:[~2013-10-03 20:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-03 19:31 precondition ssd drives w/ fio Brian L.
2013-10-03 19:52 ` Roger Sibert
2013-10-03 20:06 ` David Nellans [this message]
2013-10-03 20:42 ` Juergen Salk
2013-10-03 21:09 ` Brian L.
2013-10-03 21:39 ` Jeffrey Mcvay (jmcvay)
2013-10-04 5:44 ` Georg Schönberger
2013-10-04 17:35 ` Brian L.
2013-10-04 18:22 ` Brian L.
2013-10-04 20:16 ` Jeffrey Mcvay (jmcvay)
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=524DCE29.3050808@nellans.org \
--to=david@nellans.org \
--cc=brianclam@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox