From: John Goerzen <jgoerzen@complete.org>
Subject: Re: Live performance tools?
Date: Tue, 14 Aug 2007 13:03:39 -0500
Message-ID: <200708141303.39663.jgoerzen@complete.org>
References: <slrnfc1j28.fcc.jgoerzen@katherina.lan.complete.org>
	<46C1E8E8.3060405@ilm.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Cc: nfs@lists.sourceforge.net
To: Eli Stair <estair@ilm.com>
In-Reply-To: <46C1E8E8.3060405@ilm.com>
Sender: nfs-bounces@lists.sourceforge.net
Errors-To: nfs-bounces@lists.sourceforge.net

On Tue August 14 2007 12:39:52 pm Eli Stair wrote:
> Try lighting up an instance of ntop on the network you've got your NFS
> server(s) on.  Either span/mirror the switch ports so it sees all the
> traffic in promisc mode, or turn on sflow forwarding to the box.  As for

I was using iftop, but the traffic was too "spikey" to be able to identify 
long-term trends with it.  I'll take a look at ntop.

> determining what files are being accessed, you can use ethereal to
> capture traffic on the wire and analyze file ops occuring, but it's not
> fun to try and analyze #ops/file... you'd have to filter quite well,

Yes, that's exactly the problem I was fearing.

> You could also start up inotify on the linux NFS server, watching the
> entire directory tree you're exporting via NFS, log the output, and

Oh, EXCELLENT idea.  I don't know why I didn't think of that.  That could be 
very useful indeed.

I'm not familiar with ganglia, cacti, or monami, but will investigate.

Thanks very much for the suggestions.  This will be helpful.

-- John

-------------------------------------------------------------------------
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