All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eli Stair <estair@ilm.com>
To: John Goerzen <jgoerzen@complete.org>
Cc: nfs@lists.sourceforge.net
Subject: Re: Live performance tools?
Date: Tue, 14 Aug 2007 10:39:52 -0700	[thread overview]
Message-ID: <46C1E8E8.3060405@ilm.com> (raw)
In-Reply-To: <slrnfc1j28.fcc.jgoerzen@katherina.lan.complete.org>


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 
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, 
dump as XML/text and do some post-processing to generate your stats.

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 
later analyze the file ops as reported.  Maybe you should turn on some 
trending/monitoring of the clients themselves, I'd suggest ganglia for 
ease-of-deployment, but you could also use net-snmp and cacti, or 
monami... there are a number of ways to get data on traffic occuring at 
both ends of the transaction.

There's also an ncurses-based traffic tool that's sometimes handy for 
looking at NFS, but I don't recall its name offhand.


/eli

John Goerzen wrote:
> Hi,
> 
> We are deploying a number of Linux desktop clients running NFS against
> our Linux NFS server.  We are seeing occasional odd spikes in traffic
> that are causing performance troubles for all users.  We are trying to
> isolate the cause of these spikes, but to date haven't been able to.
> The best we can do is use iostat and verify that yes, the disk we
> expected is seeing a lot of traffic.
> 
> nfsd threads seem to be impervious to lsof.  top also doesn't show much
> about them, and of course you can't strace them.
> 
> Is there any tool out there that could give us any of this sort of info:
> 
>  * What IP addresses are generating high volumes of read or write
>    traffic
> 
>  * What files on disk are being accessed frequently via NFS
> 
>  * Anything else that could help us pinpoint the trouble
> 
> nfsstat does not seem to provide fine enough detail for this.
> 
> Thanks,
> 
> -- 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
> 


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

  reply	other threads:[~2007-08-14 17:39 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 [this message]
2007-08-14 18:03   ` John Goerzen
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=46C1E8E8.3060405@ilm.com \
    --to=estair@ilm.com \
    --cc=jgoerzen@complete.org \
    --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 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.