From: Yannis Klonatos <klonatos@ics.forth.gr>
To: xfs@oss.sgi.com
Subject: Metadata hit ratio
Date: Thu, 24 Jun 2010 23:30:44 +0300 [thread overview]
Message-ID: <4C23C074.5080100@ics.forth.gr> (raw)
Hello all,
Along with my other (yet pending :-( ) question/issue, I have
another question (i hope this is the last :-) )
now.
I would like to measure the hit ratio of the metadata accesses
of XFS (inode+internal buffers). It is my
understanding that XFS uses its own data structures, and does not rely
on the buffercache mechanisms of
the Linux kernel. However, even doing so, there may be cases that the
metadata may not fit in the RAM,
and I/O operations are required to fetch them from the underlying
storage. I have found out that there are
two places that XFS uses the submit_bio function. If i add some counters
there, would it suffice to measure all
the metadata misses?
Or is this information available in one (or more) of the
xfs_stats counters? And if so, what do i need to sum
up in order to get the total metadata hit and miss ratio?
Thanks (again!) in advance,
Yannis Klonatos
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2010-06-24 20:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-24 20:30 Yannis Klonatos [this message]
2010-06-25 1:15 ` Metadata hit ratio 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=4C23C074.5080100@ics.forth.gr \
--to=klonatos@ics.forth.gr \
--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