public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Danny Shavit <danny@zadarastorage.com>
Cc: xfs@oss.sgi.com
Subject: Re: xfs metadata overhead
Date: Thu, 23 Jun 2016 08:51:17 +1000	[thread overview]
Message-ID: <20160622225117.GX12670@dastard> (raw)
In-Reply-To: <CAC=x_0jDYb17Vh97Led7XXDiUMcUTJbpJ2Dw45gn=D0_w0K5VQ@mail.gmail.com>

On Wed, Jun 22, 2016 at 06:58:16PM +0300, Danny Shavit wrote:
> Hi,
> 
> We are looking for a method to estimate the size of metadata overhead for a
> given file system.
> We would like to use this value as indicator for the amount of cache memory
> a system for faster operation.
> Are there any counters that are maintained in the on-disk data
> structures like free space for examples?

No.

Right now, you'll need to take a metadump of the filesystem to
measure it. The size of the dump file will be a close indication of
the amount of metadata in the filesystem as it only contains
the filesystem metadata.

In future, querying the rmap will enable us to calculate it on the
fly, (i.e. not requiring the filesystem to be snapshotted/taken off
line to do a metadump).

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2016-06-22 22:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-22 15:58 xfs metadata overhead Danny Shavit
2016-06-22 22:51 ` Dave Chinner [this message]
2016-06-23 15:04   ` Danny Shavit
2016-06-23 18:12     ` Eric Sandeen
     [not found]       ` <CAC=x_0hnGQHAenv985+FusWxK_63AatB_XK_mqbAmyt=OxqYrg@mail.gmail.com>
2016-06-24 13:17         ` Eric Sandeen
2016-06-24 13:21           ` Danny Shavit
2016-06-24 22:51             ` 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=20160622225117.GX12670@dastard \
    --to=david@fromorbit.com \
    --cc=danny@zadarastorage.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