From: Yusuf Goolamabbas <yusufg@outblaze.com>
To: Ion Badulescu <ionut@badula.org>
Cc: Alan Powell <lakerfaniam2@yahoo.com>,
Steve Dickson <SteveD@RedHat.com>,
nfs@lists.sourceforge.net
Subject: Re: nfsd tuning - please help me!
Date: Mon, 17 Feb 2003 10:59:22 +0800 [thread overview]
Message-ID: <20030217025922.GA20685@outblaze.com> (raw)
In-Reply-To: <200302142032.h1EKWCIJ006931@buggy.badula.org>
Maybe RH can put their kernel's through a fstress routine
http://www.cs.duke.edu/ari/fstress/
According to the author Darell Anderson,
http://docs.freebsd.org/cgi/getmsg.cgi?fetch=1126014+0+archive/2003/freebsd-current/20030216.freebsd-current
It can emulates SPECsfs
> > Unfortunately, we've tried all that already. So given
> > that we are not hardware/network constrained, does all
> > this mean that the Linux kernel NFS runs into
> > performance issues beyond 100 file reads/sec?
>
> It's quite possible...
>
> What I'd recommend, however, is testing this again with a non-RedHat
> kernel on the client. More precisely, try running 2.4.20 plus the
> NFSALL patch from Trond's site <http://www.fys.uio.no/~trondmy/src/>.
>
> We've had significant performance problems over here with the RedHat
> kernels, which mostly went away when we replaced the NFS client code
> with 2.4.20+NFSALL.
>
> Hope this helps,
> Ion
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2003-02-17 2:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-13 22:24 nfsd tuning - please help me! Alan Powell
2003-02-14 11:33 ` Steve Dickson
2003-02-14 17:44 ` Alan Powell
2003-02-14 20:32 ` Ion Badulescu
2003-02-17 2:59 ` Yusuf Goolamabbas [this message]
2003-02-18 2:28 ` Alan Powell
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=20030217025922.GA20685@outblaze.com \
--to=yusufg@outblaze.com \
--cc=SteveD@RedHat.com \
--cc=ionut@badula.org \
--cc=lakerfaniam2@yahoo.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 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.