From: Yusuf Goolamabbas <yusufg@outblaze.com>
To: Raphael Clifford <clifford@genomes.rockefeller.edu>
Cc: nfs@lists.sourceforge.net
Subject: Re: redhat 2.4.18-5 client huge slowdown
Date: Wed, 10 Jul 2002 18:54:42 +0800 [thread overview]
Message-ID: <20020710105442.GA21856@outblaze.com> (raw)
In-Reply-To: <3D2B373E.2030602@genomes.rockefeller.edu>
Can you see if reducing rsize,wsize to 8192 seems to help
This bugzilla entry is referenced by the 2.4.18-5 kernel release note
http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=64984
Add your observations to it if it makes a difference
> I was wondering if everyone else is experiencing huge nfs write
> slowdowns using redhat kernel 2.4.18-5 (as opposed to 2.4.18-4). I am
> using a Sun Solaris machine as the server and following mount options.
>
> rw,rsize=32768,wsize=32768,nfsvers=3,proto=tcp
>
> I understand that both 2.4.18-4 and 2.4.18-5 default to 'sync' but as
> the slow down is between those versions so that shouldn't make any
> difference. I also understand that there were a lot of nfs client
> "fixes" in 2.4.18-5 so I assume they have caused this problem.
>
> The linux machine is a dual 500 MHz if that makes any difference.
>
> Cheers,
> Raphael
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Two, two, TWO treats in one.
http://thinkgeek.com/sf
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2002-07-10 10:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E17S0Jk-0006ZT-00@usw-sf-list2.sourceforge.net>
2002-07-09 19:19 ` redhat 2.4.18-5 client huge slowdown Raphael Clifford
2002-07-09 22:19 ` Tom McNeal
2002-07-10 10:54 ` Yusuf Goolamabbas [this message]
[not found] <E17SjDh-00067R-00@usw-sf-list2.sourceforge.net>
2002-07-11 19:08 ` Rex Dieter
2002-07-11 19:29 ` Rex Dieter
2002-07-12 12:07 ` Trond Myklebust
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=20020710105442.GA21856@outblaze.com \
--to=yusufg@outblaze.com \
--cc=clifford@genomes.rockefeller.edu \
--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 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.