From: Jens Axboe <axboe@kernel.dk>
To: Scott Emery <emery@sgi.com>
Cc: fio@vger.kernel.org
Subject: Re: Client - Server(s?)
Date: Tue, 31 Jul 2012 20:50:33 +0200 [thread overview]
Message-ID: <501828F9.2060100@kernel.dk> (raw)
In-Reply-To: <201207021912.q62JCqDV26291886@zion.americas.sgi.com>
On 2012-07-02 21:12, Scott Emery wrote:
> Hullo Jens,
> I have enjoyed using fio, I find it to be easy to set up and
> run.
Thanks!
> I have a question about the direction of client/server, which
> revolves around a situation I would like to benchmark. I deal with
> a couple of clustered filesystems and would like to get aggregate
> performance values based on I/O from multiple filesystem clients.
> To that end I would like to drive a test from a single "location" to
> multiple filesystem clients.
>
> My understanding (?) of fio client/server semantics is that
> one client drives no more than one server. With this understanding
> I would set up a fio server on each filesystem client that I want to
> test and then run fio clients from my test location in parallel to
> each fio server/filesystem client. I would then aggregate the
> statistics by hand. This is certainly a huge step up from scripting
> something myself by hand.
>
> It would be convenient if I could have one client/set of clients
> work together to drive the fio servers and aggregate the statistics
> for me. Is this where fio is going?
Yes, this is where fio is going, and in fact that should already work.
One fio client can drive multiple servers, you just give it the
hostnames. There's some non-intuitive ways around how it sends the same
config file and not one per server, but that's mainly parsing stuff.
It doesn't have anything to do with how fio functions, so it could
easily be changed.
Fio will also collect and sum the results, if you ask it to.
--
Jens Axboe
prev parent reply other threads:[~2012-07-31 18:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-02 19:12 Client - Server(s?) Scott Emery
2012-07-31 18:50 ` Jens Axboe [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=501828F9.2060100@kernel.dk \
--to=axboe@kernel.dk \
--cc=emery@sgi.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