From: "J. Bruce Fields" <bfields@fieldses.org>
To: Kevin Constantine
<Kevin.Constantine-FfNkGbSheRGpB8w63BLUukEOCMrvLtNR@public.gmane.org>
Cc: Chuck Lever <chuck.lever@oracle.com>, linux-nfs@vger.kernel.org
Subject: Re: nfsstat --sleep=#
Date: Thu, 12 Mar 2009 12:48:18 -0400 [thread overview]
Message-ID: <20090312164818.GF2081@fieldses.org> (raw)
In-Reply-To: <49B93C10.5020208-P5ys19MLBK/QT0dZR+AlfA@public.gmane.org>
On Thu, Mar 12, 2009 at 09:45:04AM -0700, Kevin Constantine wrote:
> J. Bruce Fields wrote:
>> On Thu, Mar 12, 2009 at 12:08:57PM -0400, Chuck Lever wrote:
>>> On Mar 12, 2009, at Mar 12, 2009, 11:50 AM, J. Bruce Fields wrote:
>>>> On Thu, Mar 12, 2009 at 10:00:34AM -0400, Chuck Lever wrote:
>>>>> Hi Kevin-
>>>>>
>>>>> man watch(1)
>>>> What would you watch?
>>> For example:
>>>
>>> watch -n3 nfsstat -c
>>>
>>> You can also use the "-d" option to highlight the differences between
>>> the current sample and the previous sample.
>>
>> He was asking for deltas; the above only gives cumulative totals.
>>
>> There's no accurate one-line solution using the existing nfsstat
>> commandline, but it should be easy to add.
>>
>
> Something like this sort of works:
> watch -n 1 'nfsstat --since /tmp/stats; nfsstat >/tmp/stats', but it
> feels more like a workaround than a feature.
It's also slightly inaccurate, since it misses any activity that
happened in the brief time between the two invocations.
> Using watch doesn't allow you to see what happened in the past either.
>
> Moving to a listed output format instead of the traditional nfsstat
> output (as seen below) makes it trivial with a simple grep to watch the
> stats that you really care about and ignore the rest.
I think we'd all be happy to take patches.--b.
> -kevin
>
>
>> --b.
>>
>>>> --b.
>>>>
>>>>> On Mar 11, 2009, at Mar 11, 2009, 9:37 PM, Kevin Constantine wrote:
>>>>>
>>>>>> I'd really like to have a way to output the nfsstat counters at
>>>>>> regular intervals (every 3 seconds) where the output is the
>>>>>> difference
>>>>>> between 3 seconds ago and now. Frequently I'll run a test and
>>>>>> want to
>>>>>> watch the nfs call profile throughout the course of the test.
>>>>>>
>>>>>> Does something like this already exist?
>>>>>> Are there objections to seeing a feature like this?
>>>>>>
>>>>>> I'm thinking something like:
>>>>>> nfsstat --sleep=1
>>>>>>
>>>>>> nfs v3 call: Server Client
>>>>>> total: 0 3476
>>>>>> null: 0 0
>>>>>> getattr: 0 1679
>>>>>> setattr: 0 0
>>>>>> lookup: 0 839
>>>>>> access: 0 839
>>>>>> readlink: 0 0
>>>>>> read: 0 0
>>>>>> write: 0 0
>>>>>> create: 0 0
>>>>>> mkdir: 0 0
>>>>>> symlink: 0 0
>>>>>> mknod: 0 0
>>>>>> remove: 0 0
>>>>>> rmdir: 0 0
>>>>>> rename: 0 0
>>>>>> link: 0 0
>>>>>> readdir: 0 0
>>>>>> readdirplus: 0 0
>>>>>> fsstat: 0 119
>>>>>> fsinfo: 0 0
>>>>>> pathconf: 0 0
>>>>>> commit: 0 0
>>>>>>
>>>>>> --
>>>>>> To unsubscribe from this list: send the line "unsubscribe linux-nfs"
>>>>>> in
>>>>>> the body of a message to majordomo@vger.kernel.org
>>>>>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>>>> --
>>>>> Chuck Lever
>>>>> chuck[dot]lever[at]oracle[dot]com
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> To unsubscribe from this list: send the line "unsubscribe
>>>>> linux-nfs" in
>>>>> the body of a message to majordomo@vger.kernel.org
>>>>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>> --
>>> Chuck Lever
>>> chuck[dot]lever[at]oracle[dot]com
>>>
>>>
>>>
>>>
>>> --
>>> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
>>> the body of a message to majordomo@vger.kernel.org
>>> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-03-12 16:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-12 1:37 nfsstat --sleep=# Kevin Constantine
[not found] ` <49B86744.6060105-P5ys19MLBK/QT0dZR+AlfA@public.gmane.org>
2009-03-12 1:58 ` Greg Banks
2009-03-12 1:58 ` Kevin Constantine
2009-03-12 14:00 ` Chuck Lever
2009-03-12 15:50 ` J. Bruce Fields
2009-03-12 16:08 ` Chuck Lever
2009-03-12 16:24 ` J. Bruce Fields
2009-03-12 16:34 ` Chuck Lever
2009-03-12 16:45 ` Kevin Constantine
[not found] ` <49B93C10.5020208-P5ys19MLBK/QT0dZR+AlfA@public.gmane.org>
2009-03-12 16:48 ` J. Bruce Fields [this message]
2009-03-12 17:09 ` Kevin Constantine
2009-03-12 17:22 ` Chuck Lever
2009-03-12 19:32 ` J. Bruce Fields
2009-03-12 20:24 ` Chuck Lever
2009-03-16 16:18 ` Steve Dickson
[not found] ` <49BE7BD6.3050303-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
2009-03-16 16:33 ` Chuck Lever
2009-03-12 16:54 ` Chuck Lever
2009-03-12 16:19 ` Greg Banks
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=20090312164818.GF2081@fieldses.org \
--to=bfields@fieldses.org \
--cc=Kevin.Constantine-FfNkGbSheRGpB8w63BLUukEOCMrvLtNR@public.gmane.org \
--cc=chuck.lever@oracle.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