From: Jens Axboe <jaxboe@fusionio.com>
To: "fio@vger.kernel.org" <fio@vger.kernel.org>
Subject: Fio 1.52
Date: Fri, 29 Apr 2011 11:44:36 +0200 [thread overview]
Message-ID: <4DBA8884.5040605@fusionio.com> (raw)
Hi,
I have tagged version 1.52 of fio. There's not much exciting since
1.51, but one change in particular warrants a note.
As of 1.52, the random generator used for generating IO offset
for random workloads has been changed. We used to rely on
the one supplied by glibc (and similar on other platforms),
but this has a few down sides:
- We did not necessarily generate the same sequences on
all platforms.
- Our internal generator is faster and from some testing
of higher quality than the glibc provided one.
So on the plus side we now generate the same IO patterns
on all platforms. The only real downside is that we do not
generate the same IO patterns as 1.51 and previous. This
_should_ not cause any issues, since the pattern should be
equally random. But it will be different. So it is something
to keep in mind, if people use fio for regression runs and
watch performance. We are not at the point where manufacturers
will optimize for a fio workload, so I don't envision any
issues from this change :-)
--
Jens Axboe
reply other threads:[~2011-04-29 9:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4DBA8884.5040605@fusionio.com \
--to=jaxboe@fusionio.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.