public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Nathan Scott <nscott@aconex.com>
To: Michael Nishimoto <miken@agami.com>
Cc: David Chinner <dgc@sgi.com>, xfs@oss.sgi.com
Subject: Re: Reducing memory requirements for high extent xfs files
Date: Tue, 26 Jun 2007 11:26:15 +1000	[thread overview]
Message-ID: <1182821175.15488.64.camel@edge.yarra.acx> (raw)
In-Reply-To: <467C620E.4050005@agami.com>

Hi Mike,

On Fri, 2007-06-22 at 16:58 -0700, Michael Nishimoto wrote:
> >  > Also, should we consider a file with 1MB extents as
> >  > fragmented?  A 100GB file with 1MB extents has 100k extents.
> > 
> > Yes, that's fragmented - it has 4 orders of magnitude more extents
> > than optimal - and the extents are too small to allow reads or
> > writes to acheive full bandwidth on high end raid configs....
> 
> Fair enough, so multiply those numbers by 100 -- a 10TB file ...

This seems a flawed way to look at this to me - in practice, almost
noone would have files that large.  While filesystem sizes increase
and can be expected to continue to increase, I'd expect individual
file sizes do not tend to increase anywhere near as much - file sizes
tend to be an application property, and apps want to work for all
filesystems.  So, people want to store _more_ files in their larger
filesystems, not _larger_ files, AFAICT.

So, IMO, this isn't a good place to invest effort - there are alot
of bigger bang-for-buck places that XFS could do with change to make
it generally much better.  The biggest probably being the amount of
log traffic that XFS generates ... that really needs to be tackled.

cheers.

--
Nathan

      parent reply	other threads:[~2007-06-26  1:27 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-30 16:49 Reducing memory requirements for high extent xfs files Michael Nishimoto
2007-05-30 22:55 ` David Chinner
2007-06-05 22:23   ` Michael Nishimoto
2007-06-05 23:11     ` Vlad Apostolov
2007-06-05 23:17       ` Vlad Apostolov
2007-06-06  1:36     ` David Chinner
2007-06-06  2:00       ` Vlad Apostolov
2007-06-06  2:05         ` Vlad Apostolov
2007-06-06 17:18       ` Michael Nishimoto
2007-06-06 23:47         ` David Chinner
2007-06-22 23:58           ` Michael Nishimoto
2007-06-25  2:47             ` David Chinner
2007-06-26  1:26             ` Nathan Scott [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=1182821175.15488.64.camel@edge.yarra.acx \
    --to=nscott@aconex.com \
    --cc=dgc@sgi.com \
    --cc=miken@agami.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