public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Theodore Tso <tytso@mit.edu>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Cc: cmm@us.ibm.com, sandeen@redhat.com, linux-ext4@vger.kernel.org
Subject: Re: [PATCH] ext4: Fix small file fragmentation
Date: Fri, 15 Aug 2008 09:38:03 -0400	[thread overview]
Message-ID: <20080815133803.GL13048@mit.edu> (raw)
In-Reply-To: <20080814231816.GA13048@mit.edu>

Here's an interesting data point.  Using Chris Mason's compilebench:

http://oss.oracle.com/~mason/compilebench

If I use:

./compilebench  -D /mnt -i 2 -r 0

on a 4GB machine such that I have plenty of memory (and nothing gets
forced disk due to memory pressure), I don't see hardly any of the
small file fragmentation problem (0.8% of the inodes in use on the
filesystem.  This is with your patch applied.

However, if I use:

./compilebench  -D /mnt -i 10 -r 0

so that data blocks are getting pushed out due to memory pressure,
then I see plenty of non-contiugous inodes (8.1% of the inodes in use
on the filesystem).  So with your patch applied, it seems that we
still have a problem related to delayed allocation and how the VM
system is doing its page cleaning.

						- Ted

  parent reply	other threads:[~2008-08-15 13:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-14 17:44 [PATCH] ext4: Fix small file fragmentation Aneesh Kumar K.V
2008-08-14 22:16 ` Mingming Cao
     [not found] ` <20080814231816.GA13048@mit.edu>
2008-08-15 13:38   ` Theodore Tso [this message]
2008-08-15 16:31     ` Aneesh Kumar K.V
2008-08-15 16:33       ` Aneesh Kumar K.V
2008-08-15 17:52   ` Aneesh Kumar K.V
2008-08-15 18:07     ` Aneesh Kumar K.V
2008-08-15 20:05       ` Theodore Tso
2008-08-16  4:43         ` Aneesh Kumar K.V
2008-08-16 10:43     ` Aneesh Kumar K.V

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=20080815133803.GL13048@mit.edu \
    --to=tytso@mit.edu \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=cmm@us.ibm.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=sandeen@redhat.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