From: bfields@fieldses.org (J. Bruce Fields)
To: Pankaj Singh <psingh.ait@gmail.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: Max connurent connections limit on nfsvs server.
Date: Fri, 23 Oct 2015 14:25:06 -0400 [thread overview]
Message-ID: <20151023182506.GB15564@fieldses.org> (raw)
In-Reply-To: <CAPrqf91BcyKjsHMK+fYm6cbxEkeU__2NYF=XZhL+TAmZ-LnzMw@mail.gmail.com>
On Fri, Oct 23, 2015 at 12:07:40PM +0530, Pankaj Singh wrote:
> I am new to nfs.
> What would be the max connurent connections an nfsv3 server can support?
> Even if we are an high end hardware and fastest(have high throughput)
> underlining file system.
I don't think we can give a single number, you may hit different limits
depending on your hardware and workload.
Note that there are max_connections tunables for both nfsd and nlm
(/porc/fs/nfsd/max_connections and
/sys/module/lockd/parameters/nlm_max_connections) which you may need to
adjust (but of course that doesn't solve all problems, it just controls
some code that causes the server to drop connections past those limits.)
--b.
next prev parent reply other threads:[~2015-10-23 18:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-23 6:37 Max connurent connections limit on nfsvs server Pankaj Singh
2015-10-23 18:25 ` J. Bruce Fields [this message]
2015-10-26 4:33 ` Pankaj Singh
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=20151023182506.GB15564@fieldses.org \
--to=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
--cc=psingh.ait@gmail.com \
/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