From: "Jarle Bjørgeengen" <jarle.bjorgeengen@usit.uio.no>
To: fio@vger.kernel.org
Subject: blktrace with fio replay for benchmarking vendor offerings
Date: Wed, 16 May 2012 21:21:11 +0200 [thread overview]
Message-ID: <4FB3FE27.3030302@usit.uio.no> (raw)
Hello,
I'm involved in the purchasing process of block storage systems, and
research viable benchmarking strategies for specifying and verifying
performance requirements.
Ideally I would like to capture our traces of our current daily
production workload with blktrace, attach the traces to the tender and
require the configuration to be able to run 2x that kind of workload.
During acceptance I would like to hook enough hardware to saturate the
system with the same workload, and measure that the requirement has been
met.
I'm interested in comments about the practical viability of such
approach if anyone have similar experiences.
Some open questions:
How safe is it to run blktrace on critical production environment? What
precautions should be made?
Given that the current system consists of 3 HP EVA800 with X number of
LUNS about 50 hosts, and the new system likely is a single system with 5
new servers running at at full speed, how much value will the benchmark
provide compared to "real world" ? Should I create equally many luns and
distribute load across the 5 machines?
Is it best to scale the workload to 2X replaying all traces
simultanously with one fio-trace-replay/lun, and then dublicate alle
replays so that each lun serves two fio-replays rather than one, and
then 3 and so on.
Any thoughts or comments are very much appreciated.
Best regards
Jarle Bj�rgeengen
University of Oslo / USIT
next reply other threads:[~2012-05-16 19:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-16 19:21 Jarle Bjørgeengen [this message]
2012-05-16 21:10 ` blktrace with fio replay for benchmarking vendor offerings Jiri Horky
2012-05-17 16:16 ` Jarle Bjørgeengen
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=4FB3FE27.3030302@usit.uio.no \
--to=jarle.bjorgeengen@usit.uio.no \
--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.