From: "J. Bruce Fields" <bfields@fieldses.org>
To: Carsten Aulbert
<carsten.aulbert-l1a6w7hxd2yELgA04lAiVw@public.gmane.org>
Cc: nfs@lists.sourceforge.net
Subject: Re: [NFS] How to set-up a Linux NFS server to handle massive number of requests
Date: Tue, 15 Apr 2008 09:58:22 -0400 [thread overview]
Message-ID: <20080415135822.GA32218@fieldses.org> (raw)
In-Reply-To: <48044055.2060500-l1a6w7hxd2yELgA04lAiVw@public.gmane.org>
On Tue, Apr 15, 2008 at 07:42:45AM +0200, Carsten Aulbert wrote:
> By the ways, discussing this issue with my colleague cluster admins, the
> question popped up, if there is a guideline/rule of thump of how many
> nfsd one should run - or asking the other way round, how to arrive at a
> good compromise.
>
> Our server boxes are pretty big (8 cores, 16 GB memory, 16 disk
> Areca1261 RAID6), so the resources used by the nfsd are not much of an
> issue - I even tested with 1024 nfsd idling around. AT some point
> increasing the number does not make much sense because I cannot get the
> data out fast enough or the seeks will likely "kill" the box^Wperformance.
>
> Any thoughts on that?
The only advice I know of is to check the "th" line in
/proc/net/rpc/nfsd and adjust the number of threads until you can verify
that they're rarely all in use; see
http://nfs.sourceforge.net/nfs-howto/ar01s05.html#nfsd_daemon_instances
--b.
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
_______________________________________________
Please note that nfs@lists.sourceforge.net is being discontinued.
Please subscribe to linux-nfs@vger.kernel.org instead.
http://vger.kernel.org/vger-lists.html#linux-nfs
next prev parent reply other threads:[~2008-04-15 13:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-10 12:12 [NFS] How to set-up a Linux NFS server to handle massive number of requests Carsten Aulbert
[not found] ` <47FE044A.7020008-l1a6w7hxd2yELgA04lAiVw@public.gmane.org>
2008-04-11 23:07 ` J. Bruce Fields
2008-04-12 6:45 ` Carsten Aulbert
[not found] ` <48005A78.9090609-l1a6w7hxd2yELgA04lAiVw@public.gmane.org>
2008-04-14 17:06 ` J. Bruce Fields
2008-04-15 4:48 ` Tom Tucker
[not found] ` <1208234913.17169.50.camel-SMNkleLxa3ZimH42XvhXlA@public.gmane.org>
2008-04-15 5:42 ` Carsten Aulbert
[not found] ` <48044055.2060500-l1a6w7hxd2yELgA04lAiVw@public.gmane.org>
2008-04-15 13:58 ` J. Bruce Fields [this message]
2008-04-16 2:49 ` Tom Tucker
2008-04-15 15:12 ` J. Bruce Fields
2008-04-16 2:43 ` Tom Tucker
[not found] ` <1208313790.3521.32.camel-SMNkleLxa3ZimH42XvhXlA@public.gmane.org>
2008-04-16 2:58 ` J. Bruce Fields
2008-04-16 3:22 ` Tom Tucker
[not found] ` <1208316166.3521.42.camel-SMNkleLxa3ZimH42XvhXlA@public.gmane.org>
2008-04-16 13:45 ` Chuck Lever
2008-04-16 14:35 ` Carsten Aulbert
2008-05-01 19:47 ` Dean Hildebrand
2008-05-01 19:51 ` J. Bruce Fields
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=20080415135822.GA32218@fieldses.org \
--to=bfields@fieldses.org \
--cc=carsten.aulbert-l1a6w7hxd2yELgA04lAiVw@public.gmane.org \
--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.