From: Steve Dickson <SteveD@RedHat.com>
To: "Brent M. Clements" <bclem@rice.edu>, nfs@lists.sourceforge.net
Subject: Re: NFS Benchmarking tests?
Date: Tue, 11 Mar 2003 06:41:41 -0500 [thread overview]
Message-ID: <3E6DCB75.7080807@RedHat.com> (raw)
In-Reply-To: <Pine.GSO.4.33.0303101405340.4041-100000@is.rice.edu>
Try http://www.cs.duke.edu/ari/fstress/
It seems to do a good job on server benchmarking.
SteveD.
Brent M. Clements wrote:
>What are some good NFS Benchmarking tests that I could run.
>
>I already know the generic answers, such as use iozone, or use this or
>that...Could I get some specifics? I need to test the throughput of 1
>node, 16 nodes, 32 nodes and so on and so on.
>
>Thanks,
>Brent
>
>
>
>
>
>-------------------------------------------------------
>This sf.net email is sponsored by:ThinkGeek
>Welcome to geek heaven.
>http://thinkgeek.com/sf
>_______________________________________________
>NFS maillist - NFS@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/nfs
>
>
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2003-03-11 11:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-10 16:32 (no subject) Lever, Charles
2003-03-10 20:06 ` NFS Benchmarking tests? Brent M. Clements
2003-03-11 11:41 ` Steve Dickson [this message]
[not found] <E18sobq-0001wN-00@sc8-sf-list2.sourceforge.net>
2003-03-11 21:25 ` Wendy Cheng
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=3E6DCB75.7080807@RedHat.com \
--to=steved@redhat.com \
--cc=bclem@rice.edu \
--cc=nfs@lists.sourceforge.net \
/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.