linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Risto Bell <reb@cypress.com>
To: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: FW: Yet Another NFS Performance Question
Date: Mon, 24 May 2010 15:06:04 -0700	[thread overview]
Message-ID: <4BFAF84C.5040003@cypress.com> (raw)
In-Reply-To: <A17A76CF549D0F4EBC38AD7AA7A3CBDA7675EA69FD@MUFASA.ts.odu.edu>

Kumar, Amit H. wrote:
> Context: NFSv3:
> I would like to get your input on the following NFS stats recorded on our server. I have read up this thread(http://www.opensubscriber.com/message/nfs@lists.sourceforge.net/7833588.html) describing the contents of /proc/net/rpc/nfsd;
>
> My Numbers are really high, for 'th' line in nfsd file...
> ...
> # uname -a
> Linux nfs3-io-0-3.local 2.6.18-53.1.14.el5 #1 SMP Wed Mar 5 11:37:38 EST 2008 x86_64 x86_64 x86_64 GNU/Linux
 > ...

Your clients (if close to CENTOS5.1: upgrade) may be hitting:

   https://bugzilla.redhat.com/show_bug.cgi?id=321111
   http://bugs.centos.org/view.php?id=2635

Client caching is impaired, hits server VERY much harder, more
often than necessary (slow down on clients, network, and server).

To demo: loop stat of a mounted dir's file that does not exist,
the deeper (dir depth) the better.

---------------------------------------------------------------
This message and any attachments may contain Cypress (or its
subsidiaries) confidential information. If it has been received
in error, please advise the sender and immediately delete this
message.
---------------------------------------------------------------


      reply	other threads:[~2010-05-24 22:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-24 21:18 FW: Yet Another NFS Performance Question Kumar, Amit H.
2010-05-24 22:06 ` Risto Bell [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=4BFAF84C.5040003@cypress.com \
    --to=reb@cypress.com \
    --cc=linux-nfs@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).