All of lore.kernel.org
 help / color / mirror / Atom feed
From: Valerie Clement <valerie.clement@bull.net>
To: ext4 development <linux-ext4@vger.kernel.org>
Subject: Large File Deletion Comparison (ext3, ext4, XFS)
Date: Fri, 27 Apr 2007 15:41:19 +0200	[thread overview]
Message-ID: <4631FD7F.9030008@bull.net> (raw)

As asked by Alex, I included in the test results the file fragmentation 
level and the number of I/Os done during the file deletion.

Here are the results obtained with a not very fragmented 100-GB file:

                  |     ext3       ext4 + extents      xfs
------------------------------------------------------------
  nb of fragments |     796             798             15
  elapsed time    |  2m0.306s        0m11.127s       0m0.553s
                  |
  blks read       |  206600            6416            352
  blks written    |   13592           13064            104
------------------------------------------------------------


And with a more fragmented 100-GB file:

                  |     ext3       ext4 + extents       xfs
------------------------------------------------------------
  nb of fragments |   20297           19841            234
  elapsed time    | 2m18.914s        0m27.429s      0m0.892s
                  |
  blks read       |  225624           25432            592
  blks written    |   52120           50664            872
------------------------------------------------------------


More details on our web site:
http://www.bullopensource.org/ext4/20070404/FileDeletion.html

    Valérie

             reply	other threads:[~2007-04-27 13:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-27 13:41 Valerie Clement [this message]
2007-04-27 18:33 ` Large File Deletion Comparison (ext3, ext4, XFS) Theodore Tso
2007-04-27 20:33   ` Andreas Dilger
2007-04-27 18:51 ` Alex Tomas
2007-04-27 20:38 ` Andreas Dilger
2007-04-27 20:48   ` Alex Tomas

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=4631FD7F.9030008@bull.net \
    --to=valerie.clement@bull.net \
    --cc=linux-ext4@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.