From: David Rees <dbr@greenhydrant.com>
To: nfs@lists.sourceforge.net
Subject: Re: Horrible NFS read performance between 2.4.18/19?
Date: Wed, 21 Aug 2002 21:58:29 -0700 [thread overview]
Message-ID: <20020821215829.A2510@greenhydrant.com> (raw)
In-Reply-To: <20020821205915.A2190@greenhydrant.com>; from dbr@greenhydrant.com on Wed, Aug 21, 2002 at 08:59:16PM -0700
Following up to myself...
On Wed, Aug 21, 2002 at 08:59:16PM -0700, David Rees wrote:
>
> The problem is that using any rsize/wsize combination larger that 2048
> results in the nfs clients getting horrible read performance. The defaults
> worked fine with the client/server ran 2.4.18 with the NFS-ALL patch. I
> have not tried updated the clients to 2.4.19, but that is the next step.
> Write performance is fine.
Upgrading the client to 2.4.19 restored read performance...
-Dave
-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone? Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
prev parent reply other threads:[~2002-08-22 4:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-22 3:59 Horrible NFS read performance between 2.4.18/19? David Rees
2002-08-22 4:58 ` David Rees [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=20020821215829.A2510@greenhydrant.com \
--to=dbr@greenhydrant.com \
--cc=nfs@lists.sourceforge.net \
/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