From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Andrey Borzenkov <arvidjaar@mail.ru>
Cc: linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: How to monitor Linux NFS client load?
Date: Sat, 11 Jul 2009 18:44:27 -0400 [thread overview]
Message-ID: <1247352267.7281.2.camel@heimdal.trondhjem.org> (raw)
In-Reply-To: <200907112103.27082.arvidjaar@mail.ru>
On Sat, 2009-07-11 at 21:03 +0400, Andrey Borzenkov wrote:
> Recently we have the case of very high latencies on NFS reads as
> reported by application (SAP R/3). NFS server was NetApp FAS; according
> to NetApp statistic, average volume read latencies were in order 10ms,
> while SAP stats gave 30-50ms. Systems were interconnected by dedicated
> 1Gb/s Cisco switches (3750G) with ca. 30% max load on interfaces.
>
> On advice of my colleague we changed sunrpc.tcp_slot_table_entries from
> default 16 to 128 which seemed to make situation much better - without
> changing load pattern of filer in any visible way.
>
> Now, I can understand, why we observed much higher latency on system and
> why changing (what effectively is) queue depth helped. But I am totally
> frustrated that there does not appear to be *any* possibility to detect
> this situation on Linux side and to get a real numbers of real NFS IO
> latencies or number of requests waiting to be executed (and I do not
> even dream about per-mount point stats).
>
> I am grateful for any hints how can we monitor Linux NFS client and get
> real-life numbers of what happens inside. Thank you!
See the nfs-iostat utility in the nfs-utils package:
http://git.linux-nfs.org/?p=steved/nfs-utils.git;a=blob;f=tools/nfs-iostat/nfs-iostat.py;h=9626d42609b9485c7fda0c9ef69d698f9fa929fd;hb=HEAD
Trond
next prev parent reply other threads:[~2009-07-11 22:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-11 17:03 Andrey Borzenkov
2009-07-11 22:44 ` Trond Myklebust [this message]
2009-07-11 22:49 ` Trond Myklebust
2009-07-12 4:38 ` Andrey Borzenkov
2009-07-12 16:30 ` Trond Myklebust
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=1247352267.7281.2.camel@heimdal.trondhjem.org \
--to=trond.myklebust@fys.uio.no \
--cc=arvidjaar@mail.ru \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®