All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Dickson <SteveD@redhat.com>
To: Peter Staubach <staubach@redhat.com>
Cc: Neil Brown <neilb@suse.de>,
	Andrew Richardson <chardson@umich.edu>,
	nfs@lists.sourceforge.net, 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:42:16 -0400	[thread overview]
Message-ID: <46B0E218.6090703@RedHat.com> (raw)
In-Reply-To: <46B0C92C.3020807@redhat.com>



Peter Staubach wrote:
> david m. richter wrote:
>>> david m. richter wrote:
>>>     
>>>> 	Hello, Neil,
>>>>
>>>> 	This set of patches adds -D/--diff-stat to nfsstat.  When this flag is
>>>> used, instead of printing out the current total statistics and exiting,
>>>> nfsstat takes a snapshot of the current statistics and pauses until the user
>>>> types ^C, at which point a second snapshot is taken and only the difference
>>>> between the two is printed; i.e., only the statistics gathered during the
>>>> pause.
>>>>       
>>> Hi.
>>>
>>> Perhaps I am missing something, but is something that we really need
>>> to complicate the nfsstat support with?  Is this not easy enough to
>>> do with already existing tools or some easily written support in sh
>>> or perl or awk or name your favorite administrative scripting language?
>>>
>>>    Thanx...
>>>
>>>       ps
>>>     
>> 	
>> 	hello, peter,
>>
>> 	yes.  :)  right now, there's no easy way to run a test and get 
>> stats for just that test, since the counters persist -- so you have to do 
>> things like run a test, unmount, remount, etc.  this is a quick way to get 
>> stats collected over an arbitrary period.  and it's not very complicated, 
>> really.
>>
>> 	i don't think a shell/perl/python/etc script would be anywhere as 
>> useful a substitute.  and with neil's suggestion about adding an optional 
>> timeout to make it easier to use -in- scripts, i think we're on the right 
>> track with this approach.
>>
>> 	.. thoughts/ideas?
> 
> It doesn't seem very complicated to me to store the output from two
> nfsstat commands and then write a small script or whatever to parse
> them and create output with the differences.
> 
> This would address the issues with wanting to be able to measure
> the statistics for a particular duration or for the duration that
> a particular problem runs.  Either would be easy to do.
> 
> Now, if someone was proposing a way to do "nfsstat 5" and make the
> output look useful, then I would be behind that 100%.
In a way we already have that... do 'watch nfsstat -c' I think
you get what your looking for...


steved.

-------------------------------------------------------------------------
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/
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

      parent reply	other threads:[~2007-08-01 19:42 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
2007-08-01 20:16             ` Steve Dickson
2007-08-01 20:54               ` Chuck Lever
2007-08-01 19:42       ` Steve Dickson [this message]

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=46B0E218.6090703@RedHat.com \
    --to=steved@redhat.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.