From: Jan Dittmer <j.dittmer@portrix.net>
To: jlnance@unity.ncsu.edu
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>,
linux-kernel@vger.kernel.org, cmp@synopsys.com
Subject: Re: Awful NFS performance with attached test program
Date: Tue, 20 Jan 2004 21:31:41 +0100 [thread overview]
Message-ID: <400D902D.8080607@portrix.net> (raw)
In-Reply-To: <20040120132803.GA2830@ncsu.edu>
[-- Attachment #1: Type: text/plain, Size: 1165 bytes --]
jlnance@unity.ncsu.edu wrote:
> On Mon, Jan 19, 2004 at 04:53:46PM -0500, Trond Myklebust wrote:
>
>
>>So you are surprised that writing the same dataset by putting one
>>integer onto each kernel page takes much more time than placing the
>>entire dataset onto just a few kernel pages? 'cos I'm not...
>
>
> I must admit that I am. I could see that it would take somewhat longer
> because a logicial way for the kernel to implement this would be as a
> read-modify-write operation. So a 2X slowdown would not supprise me.
> But the slowdown is more than 10X, and that does.
>
> Also, for what its worth, Solaris performs like this:
>
> flame> ./a.out
> Creating file: 3.886 seconds
> Updating file: 1.259 seconds
>
> While Linux performs like this:
>
> jesse> ./a.out
> Creating file: 43.042 seconds
> Updating file: 555.796 seconds
My Client (2.6.1-mm2) against my server (2.6.1-bk6) is significantly faster:
./nfstest
Creating file: 11.607 seconds
Updating file: 35.885 seconds
Note the increase of the factor 3 only instead of 10.
nfs mount options:
rw,hard,intr,rsize=8192,wsize=8192,timeo=30,retrans=10,tcp
Thanks,
Jan
[-- Attachment #2: Type: application/pgp-signature, Size: 256 bytes --]
next prev parent reply other threads:[~2004-01-20 20:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-19 21:16 Awful NFS performance with attached test program jlnance
2004-01-19 21:53 ` Trond Myklebust
2004-01-20 13:28 ` jlnance
2004-01-20 14:12 ` Trond Myklebust
2004-01-20 20:03 ` Chris Petersen
2004-01-20 21:50 ` Trond Myklebust
2004-01-21 2:01 ` jlnance
2004-01-20 20:31 ` Jan Dittmer [this message]
[not found] <20040119211649.GA20200@ncsu.edu.suse.lists.linux.kernel>
[not found] ` <1074549226.1560.59.camel@nidelv.trondhjem.org.suse.lists.linux.kernel>
[not found] ` <20040120132803.GA2830@ncsu.edu.suse.lists.linux.kernel>
[not found] ` <1074607946.1871.37.camel@nidelv.trondhjem.org.suse.lists.linux.kernel>
2004-01-20 14:38 ` Andi Kleen
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=400D902D.8080607@portrix.net \
--to=j.dittmer@portrix.net \
--cc=cmp@synopsys.com \
--cc=jlnance@unity.ncsu.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
/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