From: "J. Bruce Fields" <bfields@fieldses.org>
To: Trond Myklebust <Trond.Myklebust@netapp.com>
Cc: Gregory Magoon <gmagoon@MIT.EDU>, linux-nfs@vger.kernel.org
Subject: Re: NFSv4 vs NFSv3 with MPICH2-1.4
Date: Fri, 29 Jul 2011 10:51:11 -0400 [thread overview]
Message-ID: <20110729145111.GG23194@fieldses.org> (raw)
In-Reply-To: <1311889677.27285.14.camel@lade.trondhjem.org>
On Thu, Jul 28, 2011 at 05:47:57PM -0400, Trond Myklebust wrote:
> On Thu, 2011-07-28 at 17:24 -0400, Gregory Magoon wrote:
> > Thanks for the tips...unfortunately, making the changes you suggest (removing
> > timeo, rsize, wsize options) doesn't seem to address the issue with MPICH2 and
> > NFSv4.
>
> Have you turned off delegations on the server? I wouldn't expect them to
> help much on an MPI workload.
Note, you can do that with "echo 0 >/proc/sys/fs/leases-enable before
starting nfsd.
> Otherwise, you might want to post a comparison of your results from
> 'nfsstat' for your workload on NFSv3 and NFSv4.
Yes.
Taking a sample of the network traffic once it gets stuck might also be
interesting.
(Wait for it to get stuck, the run "tcpdump -s0 -wtmp.pcap", let it go
for a second (longer if that doesn't get anything), then interrupt it
and send us tmp.pcap.)
Or if it gets stuck immediately, then you could start the tcpdump before
the you start your tests and capture everything. But if it doesn't get
stuck immediately that could be a ton of data.
--b.
prev parent reply other threads:[~2011-07-29 14:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-28 19:23 NFSv4 vs NFSv3 with MPICH2-1.4 Gregory Magoon
2011-07-28 20:58 ` Trond Myklebust
2011-07-28 21:24 ` Gregory Magoon
2011-07-28 21:47 ` Trond Myklebust
2011-07-28 22:01 ` Gregory Magoon
2011-07-28 22:31 ` Boaz Harrosh
2011-07-28 23:15 ` Gregory Magoon
2011-07-30 3:19 ` Boaz Harrosh
2011-07-30 3:56 ` Loewe, Bill
2011-08-02 16:19 ` Gregory Magoon
2011-08-09 23:15 ` Gregory Magoon
2011-08-10 0:54 ` Boaz Harrosh
2011-07-29 14:51 ` J. Bruce Fields [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=20110729145111.GG23194@fieldses.org \
--to=bfields@fieldses.org \
--cc=Trond.Myklebust@netapp.com \
--cc=gmagoon@MIT.EDU \
--cc=linux-nfs@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;
as well as URLs for NNTP newsgroup(s).