From: "Steinar H. Gunderson" <sgunderson@bigfoot.com>
To: nfs@lists.sourceforge.net
Subject: Re: Live performance tools?
Date: Tue, 14 Aug 2007 23:48:29 +0200 [thread overview]
Message-ID: <20070814214829.GA9996@uio.no> (raw)
In-Reply-To: <46C1E8E8.3060405@ilm.com>
On Tue, Aug 14, 2007 at 10:39:52AM -0700, Eli Stair wrote:
> 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.
blktrace might also be useful here.
/* Steinar */
--
Homepage: http://www.sesse.net/
-------------------------------------------------------------------------
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
prev parent reply other threads:[~2007-08-14 21:48 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
2007-08-14 21:48 ` Steinar H. Gunderson [this message]
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=20070814214829.GA9996@uio.no \
--to=sgunderson@bigfoot.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 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.