From: Xin Zhao <uszhaoxin@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Why is NFS write so slow?
Date: Mon, 21 Mar 2005 03:29:21 -0500 [thread overview]
Message-ID: <4ae3c1405032100293ff52077@mail.gmail.com> (raw)
Sorry for the dumb question.
I am trying to develop a new filesystem based on NFS, which runs in a
very fast network environment. I used the source code of NFS2, but
noticed that NFS write is very slow. Even if I changed wsize to 8192,
it still can only reach 1MB/s. I don't know why. Because the network
is extremely fast (over 100MB/s), I don't think network is the only
reason. Any other reason?
Is the NFS write synchronous? Does that means the NFS server will not
return before the data is flushed to disk? Because nfsd_write will
close the file every time, I will assume that the data will be flushed
to disk before return. However, even if I change nfsd_write to stop
closing file, the write speed is still very slow. Can someone give me
some advice about this?
Thanks in advance!
-x
next reply other threads:[~2005-03-21 8:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-21 8:29 Xin Zhao [this message]
2005-03-21 10:15 ` Why is NFS write so slow? Matthias Andree
2005-03-21 10:46 ` Raphael Jacquot
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=4ae3c1405032100293ff52077@mail.gmail.com \
--to=uszhaoxin@gmail.com \
--cc=linux-kernel@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