From: Greg Banks <gnb@melbourne.sgi.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Neil Brown <neilb@suse.de>,
Linux NFS Mailing List <nfs@lists.sourceforge.net>
Subject: Re: [PATCH 0 of 5] knfsd: miscellaneous performance-related fixes
Date: Tue, 15 Aug 2006 11:23:03 +1000 [thread overview]
Message-ID: <1155604983.16378.1843.camel@hole.melbourne.sgi.com> (raw)
In-Reply-To: <20060814214313.GE20034@fieldses.org>
On Tue, 2006-08-15 at 07:43, J. Bruce Fields wrote:
> On Wed, Aug 09, 2006 at 12:37:36PM +1000, Greg Banks wrote:
> > On Wed, 2006-08-09 at 01:49, J. Bruce Fields wrote:
> > > It'd be nice if we could avoid ripping out a working user interface that
> > > someone might be using....
> >
> > I agree, but I don't believe a) it's working or b) anyone could
> > be getting any use out of it.
>
> OK. So the advice at
>
> http://nfs.sourceforge.net/nfs-howto/ar01s05.html#nfsd_daemon_instances
>
> is wrong?
Let's see.
> Most startup scripts, Linux and otherwise, start 8 instances of nfsd.
> In the early days of NFS, Sun decided on this number as a rule of
> thumb, and everyone else copied. There are no good measures of how
> many instances are optimal, but a more heavily-trafficked server may
> require more.
Correct.
> You should use at the very least one daemon per processor, but four to
> eight per processor may be a better rule of thumb.
Wrong. This rule might work up to 4 or 8 cpus, but only by
coincidence. Try running knfsd on a 512 cpu machine; you don't
need anything like 512 to 4096 nfsd threads. A better rule of
thumb would be 1 to 4 nfsds per simultaneously active client.
Of course that number is a lot harder to measure with the server
as it stands today.
> If you are using a 2.4 or higher kernel and you want to see how
> heavily each nfsd thread is being used, you can look at the file
> /proc/net/rpc/nfsd. The last ten numbers on the th line in that file
> indicate the number of seconds that the thread usage was at that
> percentage of the maximum allowable. If you have a large number in the
> top three deciles, you may wish to increase the number of nfsd
> instances.
This is true, except that
1. the numbers are undercounted (the mechanism tends to err
towards incrementing a lower bucket), and
2. the numbers are never reset and are scaled to the number of
nfsd daemons, so to tell whether your change in the number
of nfsds was helpful you need to reload the nfsd module or
reboot.
> This is done upon starting nfsd using the number of instances as the
> command line option,
Or by echoing a number into /proc/fs/nfsd/threads.
> and is specified in the NFS startup script (/etc/rc.d/init.d/nfs on
> Red Hat) as RPCNFSDCOUNT. See the nfsd(8) man page for more
> information.
On SUSE the file is /etc/sysconfig/nfs and the variable is
USE_KERNEL_NFSD_NUMBER.
> > An earlier version of the patch left the data structures in place
> > and just reported them as zeros in the /proc file. Would that
> > be preferrable?
>
> I'm not sure that makes any difference.
Fair enough.
Greg.
--
Greg Banks, R&D Software Engineer, SGI Australian Software Group.
I don't speak for SGI.
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
prev parent reply other threads:[~2006-08-15 1:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-08 4:04 [PATCH 0 of 5] knfsd: miscellaneous performance-related fixes Greg Banks
2006-08-08 8:01 ` Neil Brown
2006-08-08 10:22 ` Greg Banks
2006-08-08 11:25 ` Neil Brown
2006-08-09 4:18 ` Greg Banks
2006-08-15 4:26 ` Neil Brown
2006-08-15 11:38 ` Greg Banks
2006-08-08 15:49 ` J. Bruce Fields
2006-08-09 2:37 ` Greg Banks
2006-08-14 21:43 ` J. Bruce Fields
2006-08-15 1:23 ` Greg Banks [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=1155604983.16378.1843.camel@hole.melbourne.sgi.com \
--to=gnb@melbourne.sgi.com \
--cc=bfields@fieldses.org \
--cc=neilb@suse.de \
--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