From: John Goerzen <jgoerzen@complete.org>
To: Eli Stair <estair@ilm.com>
Cc: nfs@lists.sourceforge.net
Subject: Re: Live performance tools?
Date: Tue, 14 Aug 2007 13:03:39 -0500 [thread overview]
Message-ID: <200708141303.39663.jgoerzen@complete.org> (raw)
In-Reply-To: <46C1E8E8.3060405@ilm.com>
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
next prev parent reply other threads:[~2007-08-14 18:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-13 21:25 Live performance tools? John Goerzen
2007-08-14 17:39 ` Eli Stair
2007-08-14 18:03 ` John Goerzen [this message]
2007-08-14 21:48 ` Steinar H. Gunderson
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=200708141303.39663.jgoerzen@complete.org \
--to=jgoerzen@complete.org \
--cc=estair@ilm.com \
--cc=nfs@lists.sourceforge.net \
/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