From: Matthias Andree <matthias.andree@gmx.de>
To: linux-kernel@vger.kernel.org
Subject: Re: Why is NFS write so slow?
Date: Mon, 21 Mar 2005 11:15:32 +0100 [thread overview]
Message-ID: <20050321101532.GA14298@merlin.emma.line.org> (raw)
In-Reply-To: <4ae3c1405032100293ff52077@mail.gmail.com>
On Mon, 21 Mar 2005, Xin Zhao wrote:
> 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?
Yes, that is the case here. You can use export or mount options to make
NFS asynchronous.
Plus, NFS3 has write clustering which may be worth a try depending on
your workload.
--
Matthias Andree
next prev parent reply other threads:[~2005-03-21 10:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-21 8:29 Xin Zhao
2005-03-21 10:15 ` Matthias Andree [this message]
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=20050321101532.GA14298@merlin.emma.line.org \
--to=matthias.andree@gmx.de \
--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
all inboxes | Powered by JetHome®