Flexible I/O Tester development
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Jiri Horky <jiri.horky@cesnet.cz>
Cc: fio@vger.kernel.org
Subject: Re: distrubuted iops measuring
Date: Mon, 26 Mar 2012 20:50:40 +0200	[thread overview]
Message-ID: <4F70BA80.9030803@kernel.dk> (raw)
In-Reply-To: <4F6F9581.9010207@cesnet.cz>

On 2012-03-26 00:00, Jiri Horky wrote:
> Hi,
> 
> I would like to measure IOPS on a distributed file system from several 
> hosts in parallel.
> I am a bit lost in what options I should use. I would like to have each 
> host in a cluster accessing its own file to not stress metadata and/or 
> locking infrastructure. I thought that on all clients, I should run just:
> 
> fio --server
> 
> And from an admin node something like
> 
> fio --client server1 job.desc.1 --client server2 job.desc.2 --client 
> server3 job.desc.3...., where job.desc.X is specific to the client 
> (different filename).
> 
> But it seems like each host executes each job file, which is not what I 
> would like...
> I bet there is a way how to accomplish this. Could you please point me 
> to the right direction?

That is/was indeed the intended idea. It's just a parsing issue that
causes it to support just one job file across a bunch of hosts, it's not
a fio limitation. So it should be relatively easy to fix. Your above
incantation ends up being identical to doing:

$ fio --client server1 --client server2 --client server3 job1 job2 job3

I can fix this when I get the time, or you can dive into it yourself if
you want. It's in init.c:parse_cmd_line().

-- 
Jens Axboe


      reply	other threads:[~2012-03-26 18:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-25 22:00 distrubuted iops measuring Jiri Horky
2012-03-26 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=4F70BA80.9030803@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=fio@vger.kernel.org \
    --cc=jiri.horky@cesnet.cz \
    /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