From: "Chuanwen Wu" <wcw8410@gmail.com>
To: gentoo-cluster@lists.gentoo.org
Cc: gentoo-user <gentoo-user@lists.gentoo.org>
Subject: [gentoo-user] Re: [gentoo-cluster] Iozone on multiple nodes using ssh
Date: Sat, 10 Jan 2009 23:50:47 +0800 [thread overview]
Message-ID: <7797aa370901100750i59a691e2u81a3b9ecf7af8865@mail.gmail.com> (raw)
In-Reply-To: <6b75ae110901100651w286ee068o122fa11186acacfa@mail.gmail.com>
Hi, thanks!
On Sat, Jan 10, 2009 at 10:51 PM, t35t0r <t35t0r@gmail.com> wrote:
>> dnfs@node73 ~ $ iozone -R -s 64k -t 1 -+m clientlist
>> [...]
>> Throughput test with 1 process
>> Each process writes a 64 Kbyte file in 4 Kbyte records
I know what you mean. I just gave the example, in the case the path of
iozone is incorrect, what would happen, And the result is the error
below will be print out:
>> bash: /tmp/iozone: No such file or directory
I just tried to proved that the path of iozone in my nodes is correct.
>
> # hostname directoryForTestFiles pathToIozoneOnEachHost
> node1 /net/NAS/awesomeFS /home/somewhere/bin/iozone
> node2 /net/NAS/awesomeFS /home/somewhere/bin/iozone
> node3 /net/NAS/awesomeFS /home/somewhere/bin/iozone
Now, I almost gave up iozone. I have tried iometer, which is better at
testing parallel fs as I know. It's very easy to config and run.
--
wcw
prev parent reply other threads:[~2009-01-10 15:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-08 15:12 [gentoo-user] Iozone on multiple nodes using ssh Chuanwen Wu
2009-01-09 15:42 ` [gentoo-user] " Chuanwen Wu
[not found] ` <6b75ae110901080904o9ee880bk561fa8c7110df401@mail.gmail.com>
[not found] ` <49680859.9020701@neuralbs.com>
[not found] ` <6b75ae110901092131t7a1fbb86k34dc537784aaef23@mail.gmail.com>
2009-01-10 10:08 ` [gentoo-user] Re: [gentoo-cluster] " Chuanwen Wu
[not found] ` <6b75ae110901100651w286ee068o122fa11186acacfa@mail.gmail.com>
2009-01-10 15:50 ` Chuanwen Wu [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=7797aa370901100750i59a691e2u81a3b9ecf7af8865@mail.gmail.com \
--to=wcw8410@gmail.com \
--cc=gentoo-cluster@lists.gentoo.org \
--cc=gentoo-user@lists.gentoo.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