From: Peter Staubach <staubach@redhat.com>
To: steve <lingxiang@huawei.com>
Cc: Lee Revell <rlrevell@joe-job.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"zhangtiger@huawei.com" <zhangtiger@huawei.com>
Subject: Re: why nfs server delay 10ms in nfsd_write()?
Date: Fri, 20 May 2005 09:05:38 -0400 [thread overview]
Message-ID: <428DE0A2.5070107@redhat.com> (raw)
In-Reply-To: <0IGS00FKJBCKRE@szxml02-in.huawei.com>
steve wrote:
>Hi Peter,
>My envionment looks like that:
>
>NFS Server：Suse9 Enterprise
>NFS Client：Redhat AS3.0(kernel 2.4.21)
>
>I made a ramdisk and export it with nfs
>Server and Client are connected with 1000Mbps
>
>mount the ramdisk on the client with parameters: -t nfs -o rw,noac
>
>then test with iometer and the parameters are:
>Outstanding IO is 32, transfer request size is 512, sequential write
>the result is about 300KB/s, iops is about 600
>
>with dd test i find the delay most cost at the server.
>
>i agree with Avi that "if the NFS client has no (or low) concurrency, then write gathering would reduce preformance"
>
I would agree too with Avi, and especially in this configuration...
I think that we could construct a writer gathering implementation which
did not
show measurable performance impact in this sort of situation though still.
Thanx...
ps
next prev parent reply other threads:[~2005-05-20 13:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-20 10:44 Re: why nfs server delay 10ms in nfsd_write()? steve
2005-05-20 13:05 ` Peter Staubach [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-05-19 2:46 steve
2005-05-19 3:08 ` Trond Myklebust
2005-05-19 3:13 ` Lee Revell
2005-05-19 12:53 ` Peter Staubach
2005-05-19 13:26 ` Trond Myklebust
2005-05-19 13:41 ` Peter Staubach
2005-05-19 13:59 ` Lee Revell
2005-05-19 14:10 ` Peter Staubach
2005-05-19 14:13 ` Avi Kivity
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=428DE0A2.5070107@redhat.com \
--to=staubach@redhat.com \
--cc=lingxiang@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rlrevell@joe-job.com \
--cc=zhangtiger@huawei.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.