From: Joe Landman <joe.landman@gmail.com>
To: xfs@oss.sgi.com
Subject: Re: gather write metrics on multiple files
Date: Thu, 09 Oct 2014 00:49:43 -0400 [thread overview]
Message-ID: <543613E7.70508@gmail.com> (raw)
In-Reply-To: <543611CF.6030904@hardwarefreak.com>
On 10/09/2014 12:40 AM, Stan Hoeppner wrote:
> Does anyone know of a utility that can track writes to files in an
> XFS directory tree, or filesystem wide for that matter, and gather
> filesystem blocks written per second data, or simply KiB/s, etc? I
> need to analyze an application's actual IO behavior to see if it
> matches what I'm being told the application is supposed to be doing.
>
We've written a few for this purpose (local IO probing).
Start with collectl (looks at /proc/diskstats), and others. Our tools
go to /proc/diskstats, and use this to compute BW and IOPs per device.
If you need to log it for a long time, set up a time series database (we
use influxdb and the graphite plugin). Then grab your favorite metrics
tool that talks to graphite/influxdb (I like
https://github.com/joelandman/sios-metrics for obvious reasons), and
start collecting data.
> Thanks, Stan
>
> _______________________________________________ xfs mailing list
> xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs
>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2014-10-09 4:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-09 4:40 gather write metrics on multiple files Stan Hoeppner
2014-10-09 4:49 ` Joe Landman [this message]
2014-10-09 5:24 ` Stan Hoeppner
2014-10-09 21:13 ` Dave Chinner
2014-10-09 22:30 ` Stan Hoeppner
2014-10-18 6:03 ` Stan Hoeppner
2014-10-18 18:16 ` Stan Hoeppner
2014-10-19 22:24 ` Dave Chinner
2014-10-21 23:56 ` Stan Hoeppner
2014-10-25 2:28 ` Stan Hoeppner
2014-10-09 21:07 ` Dave Chinner
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=543613E7.70508@gmail.com \
--to=joe.landman@gmail.com \
--cc=xfs@oss.sgi.com \
/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