All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Xin Zhao <uszhaoxin@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: NFS2 question, help, pls!
Date: Tue, 12 Apr 2005 19:10:21 -0400	[thread overview]
Message-ID: <1113347421.13102.6.camel@mindpipe> (raw)
In-Reply-To: <1113344795.10420.125.camel@lade.trondhjem.org>

On Tue, 2005-04-12 at 15:26 -0700, Trond Myklebust wrote:
> ty den 12.04.2005 Klokka 15:22 (-0400) skreiv Xin Zhao:
> > I have very very fast network and is testing NFS2 over this kind of
> > network. I noticed that for standard work like read/write a large
> > file,  compile kernels, the performance of NFS2 is good. But if I try
> > to decompress kernel tar file. The standard ext2 takes 28s while NFS2
> > takes 81s. Also, if I remove the kernel source code tree, ext2 takes
> > 19s but NFS2 takes 44s.
> > 
> > Why?  (You can assume that network is very fast. )  Is there any
> > improvements in NFS3/4 on this issue? If so, how?
> 
> NFSv2 requires the server to immediately write all data to disk before
> it can reply to the RPC write request (synchronous writes).

This behavior can be disabled with the "async" export option for NFSv2.

Lee


      reply	other threads:[~2005-04-12 23:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-12 19:22 NFS2 question, help, pls! Xin Zhao
2005-04-12 22:26 ` Trond Myklebust
2005-04-12 23:10   ` Lee Revell [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=1113347421.13102.6.camel@mindpipe \
    --to=rlrevell@joe-job.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trond.myklebust@fys.uio.no \
    --cc=uszhaoxin@gmail.com \
    /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.