From: Chuck Lever <chuck.lever@oracle.com>
To: nfs@lists.sourceforge.net
Cc: Neil Brown <neilb@suse.de>, Peter Staubach <staubach@redhat.com>,
Andrew Richardson <chardson@umich.edu>,
Alex Soule <soule@umich.edu>,
"david m. richter" <richterd@citi.umich.edu>
Subject: Re: [PATCH 0/7] nfsstat: adding -D/--diff-stat to nfsstat
Date: Wed, 01 Aug 2007 15:35:48 -0400 [thread overview]
Message-ID: <46B0E094.2080109@oracle.com> (raw)
In-Reply-To: <46B0CF5B.1000609@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2461 bytes --]
Peter Staubach wrote:
> david m. richter wrote:
>>> Now, if someone was proposing a way to do "nfsstat 5" and make the
>>> output look useful, then I would be behind that 100%.
>>>
>>> Thanx...
>>>
>>> ps
>>>
>>
>> do you mean "gather stats for the next 5 seconds"? i don't
>> understand the arg.
>
> Sorry, I should have been more explicit. I have wished for
> something that would behave like "vmstat 5", ie. print nfsstat
> statistics in some sort short hand fashion once every few
> seconds, 5 in this example.
>
> The problem has always been that there are too many operations
> for summarize them on one line in any sort of interesting way.
> This becomes particularly true for NFSv4 which has its multitude
> of operations...
>
> Perhaps we should just bite the bullet and produce the large
> output, much like "iostat 5" seems to.
First, thanks to David and the citi guys for the patches.
The kernel stats themselves should never be zeroed except by umount or
reboot. Otherwise, tools like "sar" and "iostat" that are looking
directly at the same set of kernel stats, and producing a "one every 5
seconds" type of output, would be totally confused if "nfsstat -z"
actually cleared the kernel counters.
There's a bigger picture here. nfsstat does not live in a vacuum, it
lives in the presence of all the other I/O tools like sar, vmstat, and
iostat. For that matter, we already have "watch nfsstat" and
"nfswatch". Those tools already provide a "once every 5 seconds" type
of interface. I might even be inclined to argue that adding "once every
5 seconds" type functionality is really outside of nfsstat's job
description.
So if we wanted an "nfsstat --since" or "nfsstat 5 5" kind of thing,
maybe we should think about the other tools, how they fit in, and how
they work, and see if we can use one of them for that. Even better, a
GUI like gnome-system-monitor would be very nice for watching NFS client
and server performance in real time.
I'm kind of tired of NFS living in its own little world with regard to
the other file systems. The NFS performance metrics I built were
precisely for the purpose of making NFS a "first class" file system with
regard to reporting errors and performance, and for the purpose of
including NFS in the tools sysadmins normally use to watch I/O subsystem
performance data on local disks.
Can we come up with a plan that moves NFS closer to other file systems?
[-- Attachment #2: chuck.lever.vcf --]
[-- Type: text/x-vcard, Size: 290 bytes --]
begin:vcard
fn:Chuck Lever
n:Lever;Chuck
org:Oracle Corporation;Corporate Architecture: Linux Projects Group
adr:;;1015 Granger Avenue;Ann Arbor;MI;48104;USA
title:Principal Member of Staff
tel;work:+1 248 614 5091
x-mozilla-html:FALSE
url:http://oss.oracle.com/~cel
version:2.1
end:vcard
[-- Attachment #3: Type: text/plain, Size: 315 bytes --]
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
[-- Attachment #4: Type: text/plain, Size: 140 bytes --]
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2007-08-01 19:37 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-31 21:38 [PATCH 0/7] nfsstat: adding -D/--diff-stat to nfsstat david m. richter
2007-07-31 22:11 ` Neil Brown
2007-07-31 23:29 ` david m. richter
2007-07-31 23:41 ` J. Bruce Fields
2007-08-01 0:42 ` Neil Brown
2007-08-01 11:55 ` Peter Staubach
2007-08-01 15:59 ` david m. richter
2007-08-01 16:49 ` Trond Myklebust
2007-08-01 17:07 ` J. Bruce Fields
2007-08-01 17:42 ` david m. richter
2007-08-01 16:50 ` J. Bruce Fields
2007-08-01 17:35 ` david m. richter
2007-08-01 17:41 ` J. Bruce Fields
2007-08-01 17:45 ` david m. richter
2007-08-01 17:46 ` Trond Myklebust
2007-08-01 17:48 ` david m. richter
2007-08-01 18:02 ` Trond Myklebust
2007-08-01 18:12 ` david m. richter
2007-08-01 18:15 ` Muntz, Daniel
2007-08-01 18:37 ` david m. richter
2007-08-01 18:41 ` Trond Myklebust
2007-08-01 18:47 ` david m. richter
2007-08-01 18:50 ` J. Bruce Fields
2007-08-01 20:03 ` Steve Dickson
2007-08-01 20:48 ` J. Bruce Fields
2007-08-01 21:50 ` Steve Dickson
2007-08-01 22:40 ` Trond Myklebust
2007-08-01 18:38 ` J. Bruce Fields
2007-08-01 17:52 ` J. Bruce Fields
2007-08-01 17:55 ` Peter Staubach
2007-08-01 18:14 ` david m. richter
2007-08-01 18:22 ` Peter Staubach
2007-08-01 18:25 ` david m. richter
2007-08-01 18:57 ` J. Bruce Fields
2007-08-01 19:35 ` Chuck Lever [this message]
2007-08-01 20:16 ` Steve Dickson
2007-08-01 20:54 ` Chuck Lever
2007-08-01 19:42 ` Steve Dickson
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=46B0E094.2080109@oracle.com \
--to=chuck.lever@oracle.com \
--cc=chardson@umich.edu \
--cc=neilb@suse.de \
--cc=nfs@lists.sourceforge.net \
--cc=richterd@citi.umich.edu \
--cc=soule@umich.edu \
--cc=staubach@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.