From: Fu Liankun <fuliankun@cn.fujitsu.com>
To: linux-nfs@vger.kernel.org
Subject: spnfs write performance issue
Date: Wed, 22 Feb 2012 18:16:17 +0800 [thread overview]
Message-ID: <4F44C071.8010104@cn.fujitsu.com> (raw)
When copy a big file(about 500MB) to nfs server using pnfs, it cost
obvious longer time as compared with NFSv3 or NFSv4 protocol.
PNFS cost about 300-550s
NFSv3 cost about 49s
NFSv4 cost about 49s
My test environment as following:
MDS: 3.1.0-rc8-pnfs ipaddr1: 192.168.0.100, ipaddr2:192.168.1.100
DS1: 3.1.0-rc8-pnfs ipaddr1: 192.168.0.101, ipaddr2:192.168.1.101
DS2: 3.1.0-rc8-pnfs ipaddr1: 192.168.0.102, ipaddr2:192.168.1.102
client: RHEL6.2GA(2.6.32-220.el6.i686) ipaddr1: 192.168.0.19,
ipaddr2:192.168.1.19
192.168.1.100 <-------- NFS4.1 connection --------->192.168.1.101
192.168.0.100 <-------- NFS4.1 connection --------->192.168.0.102
192.168.0.19 <-------- NFS4.1 connection --------->192.168.0.100
Dunring the write process, the client output the message:
FS-Cache: Loaded
FS-Cache: Netfs 'nfs' registered for caching
nfs4filelayout_init: NFSv4 File Layout Driver Registering...
nfs: server 192.168.1.101 not responding, timed out
The message "nfs: server 192.168.1.101 not responding, timed out" was
output during the COMMIT request.
Who can tell me the reason why pnfs cost so long time.
next reply other threads:[~2012-02-22 10:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-22 10:16 Fu Liankun [this message]
2012-02-22 17:25 ` spnfs write performance issue J. Bruce Fields
2012-02-27 6:27 ` Fu Liankun
2012-02-27 12:01 ` J. Bruce Fields
2012-02-28 1:32 ` Fu Liankun
2012-02-28 1:46 ` J. Bruce Fields
2012-02-28 1:48 ` Fu Liankun
2012-02-28 1:53 ` J. Bruce Fields
2012-02-28 2:14 ` Fu Liankun
2012-02-28 9:27 ` Benny Halevy
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=4F44C071.8010104@cn.fujitsu.com \
--to=fuliankun@cn.fujitsu.com \
--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 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.