On Mar 12, 2009, at Mar 12, 2009, 12:48 PM, J. Bruce Fields wrote:
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.
Actually I would rather see the performance metrics scripts improved.
These tools give a lot more information than nfsstat ever will be able
to.
--
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@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
