From: Nathan Scott <nathans@redhat.com>
To: Mark Seger <mjseger@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Useful stats (was Re: definitions for /proc/fs/xfs/stat)
Date: Wed, 19 Jun 2013 19:02:13 -0400 (EDT) [thread overview]
Message-ID: <1040361622.4508678.1371682933909.JavaMail.root@redhat.com> (raw)
In-Reply-To: <CAC2B=ZGm4W=oFY+8sWAefhH79qK5N7yma4qQh_AQaOGiQDUWhw@mail.gmail.com>
Hi Mark,
----- Original Message -----
> ...
> On a totally different topic, and if you like we can start a different
> thread on it, I'd be interested in adding some monitoring stats to collectl
> for xfs and could use some suggestions of what are the most important.
Did you receive any other feedback on this (offlist perhaps)? I was kinda
hoping someone else would chime in, but can share our experiences with PCP
if it helps.
We provide options to record all xfs.* metrics & an alternative to record
just the core I/O stats (so log I/O and the file read/write metrics). With
PCP one can record any subset at any rate, so those are just convenience /
default suggestions.
In terms of recording in collectl, not sure what the requirements/parameters
are for you but I'd suggest recording all the data (in save-to-disk mode),
and IIRC you've got brief/verbose reporting modes - I'd focus on the log,
file I/O and buffer I/O stats when being "brief", and expand out to showing
in-core inode/dquot stats, ail/transaction stats, dir/attr operation stats.
You might consider another very-verbose kinda view with all of the various
btree stats, but that may be going too far.
Note that these are all aggregate statistics, there has been on-and-off
discussion for many years about adding some per-filesystem XFS stats, but
to date that has not happened - perhaps someday it will, so keep that in
mind for collectl too I guess.
Also, be aware there is a separate file for quota metrics, for hysterical
raisins (/proc/fs/xfs/xqmstat).
HTH.
cheers.
--
Nathan
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-06-19 23:02 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-14 16:37 definitions for /proc/fs/xfs/stat Mark Seger
2013-06-14 22:16 ` Nathan Scott
2013-06-14 22:37 ` Mark Seger
2013-06-15 0:17 ` Nathan Scott
2013-06-15 1:55 ` Mark Seger
2013-06-15 2:04 ` Dave Chinner
2013-06-15 10:35 ` Mark Seger
2013-06-15 16:22 ` Mark Seger
2013-06-16 0:11 ` Dave Chinner
2013-06-16 12:58 ` Mark Seger
2013-06-16 22:06 ` Dave Chinner
2013-06-16 22:31 ` Mark Seger
2013-06-16 23:14 ` Dave Chinner
2013-06-16 23:31 ` Mark Seger
2013-06-17 1:11 ` Nathan Scott
2013-06-17 2:46 ` Dave Chinner
2013-06-17 5:41 ` Nathan Scott
2013-06-17 10:57 ` Mark Seger
2013-06-17 11:13 ` Dave Chinner
2013-06-17 14:57 ` Mark Seger
2013-06-17 20:28 ` Stefan Ring
2013-06-18 0:15 ` Dave Chinner
2013-06-18 10:17 ` Mark Seger
2013-06-19 23:02 ` Nathan Scott [this message]
2013-06-17 11:19 ` Dave Chinner
2013-06-17 13:18 ` Stan Hoeppner
2013-06-18 0:13 ` Mark Goodwin
2013-06-16 0:00 ` 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=1040361622.4508678.1371682933909.JavaMail.root@redhat.com \
--to=nathans@redhat.com \
--cc=mjseger@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