From: Chuck Lever <chuck.lever@oracle.com>
To: Or Gerlitz <ogerlitz@Voltaire.com>
Cc: Sebastien Godard <sysstat@orange.fr>,
Trond Myklebust <Trond.Myklebust@netapp.com>,
linux-nfs@vger.kernel.org
Subject: Re: iostat "await" like counter for measuring nfs latency
Date: Wed, 28 Jul 2010 13:40:08 -0400 [thread overview]
Message-ID: <4C506B78.7040108@oracle.com> (raw)
In-Reply-To: <4C4FFC2B.4020906@Voltaire.com>
On 07/28/10 05:45 AM, Or Gerlitz wrote:
> Trond Myklebust wrote:
>> On Tue, 2010-07-27 at 13:07 +0300, Or Gerlitz wrote:
>>> Doing some iscsi and nfs performance testing, I realized that iostat(1)
>>> doesn't support an "await" like counter for measuring nfs latency.
>>> Can tracking nfs latency be done in other means? is there a plan to
>>> extend the nfs iostats code to include such/similar counter?
>
>> The information is already available in /proc/self/mountstats. It is up
>> to iostat to start using it.
>
> Sebastian, is there a plan to support await like counter in sysstat?
>
> I didn't find a source repository (is there an open one? where?) so
> downloaded the latest code (version 9.1.3) drop from the website and
> couldn't see there such a counter, am I missing something?
There are Python scripts in nfs-utils that report the statistics in
/proc/self/mountstats. Nobody really likes the file format of
/proc/self/mountstats, so the plan is to move these, at some point, to
someplace where perf can report them.
At that point, iostat support would also be nice.
next prev parent reply other threads:[~2010-07-28 17:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-27 10:07 iostat "await" like counter for measuring nfs latency Or Gerlitz
2010-07-27 15:27 ` Trond Myklebust
2010-07-28 9:45 ` Or Gerlitz
2010-07-28 17:40 ` Chuck Lever [this message]
2010-07-28 19:21 ` Sebastien Godard
2010-07-29 15:53 ` Chuck Lever
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=4C506B78.7040108@oracle.com \
--to=chuck.lever@oracle.com \
--cc=Trond.Myklebust@netapp.com \
--cc=linux-nfs@vger.kernel.org \
--cc=ogerlitz@Voltaire.com \
--cc=sysstat@orange.fr \
/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).