From: Lee Revell <rlrevell@joe-job.com>
To: Xin Zhao <uszhaoxin@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: why is NFS performance poor when decompress linux kernel
Date: Sat, 08 Oct 2005 01:59:48 -0400 [thread overview]
Message-ID: <1128751189.17981.62.camel@mindpipe> (raw)
In-Reply-To: <4ae3c140510072139n68b9b2eeyc0a400be32d958fe@mail.gmail.com>
On Sat, 2005-10-08 at 00:39 -0400, Xin Zhao wrote:
> I noticed that when doing large file copy or linux kernel compilation
> in a NFS direcotry, the performance is not bad compared to local disk
> filesystem such as ext2. However, if I do linux kernel tarball
> decompression on a NFS directory, the performance is much worse than
> local disk filesystem (over 3 times slower). Anybody know the reason?
Because NFS requires all writes to be synchronous by default, and
uncompressing the kernel is the most write intensive of those three
operations. Mount with the async option and the performance should be
closer to a local disk. Obviously this is more dangerous.
Lee
next prev parent reply other threads:[~2005-10-08 5:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-08 4:39 why is NFS performance poor when decompress linux kernel Xin Zhao
2005-10-08 5:59 ` Lee Revell [this message]
2005-10-08 7:19 ` Willy Tarreau
2005-10-08 14:35 ` Xin Zhao
2005-10-08 15:03 ` Xin Zhao
2005-10-08 21:23 ` Willy Tarreau
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=1128751189.17981.62.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox