Re: [PATCH] NFS: Zeroing NFS and kNFSD stats

["J. Bruce Fields" <bfields@fieldses.org>]

On Tue, Jul 13, 2004 at 04:16:58PM -0400, Steve Dickson wrote:
> IMHO,  its much simpler, easier and less error prone to zero them out 
> than to make nfsstat
> take samples then calculate the differences...


Example 1:
	nfsstat -z
	nfsstat
Example 2:
	nfsstat --checkpoint foo
	nfsstat --since foo

Example 1 is indeed a little simpler to use, but not much.

If you really wanted an interface like that in case 1, you could do that
by storing the checkpointed stats in some default location.

If the typical use is just logging in and collecting a few seconds of
statistics then the easiest thing might be something like

	nfsstat -z
		Collecting statistics.... Hit ^C for results
	^C
	Server rpc stats:
	...etc.

> I just think that a bit over nfsstat's head...

I'm not sure what you mean.  It certainly shouldn't be hard to
implement.

> but I contend that the current nfsd/rpc stats simply aren't these type
> of stats... these are simple activity counters that let you know what
> (if anything) is happening... I think it would be a very difficult
> task to try to used these counts in any long term analysis... I just
> don't think they recored the right type of information for that....

It's not obvious to me why they couldn't be used over long periods.  But
even if the statistics-gathering daemon isn't a good example, I don't
see why there couldn't be other cases where more than one process might
happen to be trying to collect statistics at the same time.

--b.


-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs