linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Richardson <mcr@sandelman.ca>
To: linux-nfs@vger.kernel.org
Cc: Shyam Kaushik <shyamnfs1@gmail.com>,
	"J. Bruce Fields" <bfields@fieldses.org>
Subject: Re: Need help with NFS Server SUNRPC performance issue
Date: Thu, 31 Oct 2013 10:45:46 -0400	[thread overview]
Message-ID: <29447.1383230746@obiwan.sandelman.ca> (raw)
In-Reply-To: <20131031141538.GA621@fieldses.org>

[-- Attachment #1: Type: text/plain, Size: 1624 bytes --]


    >> I am chasing a NFS server performance issue on Ubuntu
    >> 3.8.13-030813-generic kernel. We setup 32 NFSD threads on our NFS
    >> server.

I have been also trying to figure out NFS performance issues at my home
office.  Server is ubuntu precise (3.2.0-55, old, true) kernel, and clients
are mostly a mix of Debian versions (mostly virtualized XEN).
GbE over a VLAN is setup just for storage, and mostly IPv6 connections.

J. Bruce Fields <bfields@fieldses.org> wrote:
    > Would you be willing to test an upstream kernel and/or some patches?
    > Sounds like you're using only NFSv4?

I'm also willing to; my preference would be to build a generic 3.10 or 3.11
kernel with NFS as a module, and then update the NFS code, but I
haven't gotten around to scheduling some time to reboot a bunch.

What I observe is huge TCP send queues on the server and what appears to be
head of queue blocking on the client.  This looks like a client issue to me,
and for at least one client (my mpd/shoutcast server), I'm happy to reboot
it regularly... I notice the NFS delays because the music stops :-)

There are some potential instabilities in frequency of IPv6 Router
Advertisements due to a bug in the CeroWRT, which initially I was blaming,
but I'm no longer convinced, since it happens over IPv4 on the storage VLAN
too.

Shyam, please share with me your testing strategy.

--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        | network architect  [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [






[-- Attachment #2: Type: application/pgp-signature, Size: 307 bytes --]

  reply	other threads:[~2013-10-31 14:45 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-31  6:49 Need help with NFS Server SUNRPC performance issue Shyam Kaushik
2013-10-31 14:15 ` J. Bruce Fields
2013-10-31 14:45   ` Michael Richardson [this message]
2013-10-31 15:14     ` J. Bruce Fields
2013-11-01 19:09       ` Michael Richardson
2013-11-04 23:03         ` J. Bruce Fields
2013-11-01  4:43     ` Shyam Kaushik
2013-11-13  4:07     ` Shyam Kaushik
2013-11-13 16:18       ` Bruce Fields
2013-11-01  4:38   ` Shyam Kaushik
2013-11-04 23:02     ` J. Bruce Fields
2013-11-05 13:44       ` Shyam Kaushik
2013-11-05 19:58         ` J. Bruce Fields
2013-11-06  7:27           ` Shyam Kaushik
2013-11-13 16:24             ` J. Bruce Fields
2013-11-13 22:00               ` J. Bruce Fields
2013-11-14  4:23                 ` Shyam Kaushik

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=29447.1383230746@obiwan.sandelman.ca \
    --to=mcr@sandelman.ca \
    --cc=bfields@fieldses.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=shyamnfs1@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;
as well as URLs for NNTP newsgroup(s).