From: Bruce Guenter <lists-linux-ext4@bruce-guenter.dyndns.org>
To: linux-ext4@vger.kernel.org
Subject: Re: ext4 unlink performance
Date: Fri, 14 Nov 2008 09:48:48 -0600 [thread overview]
Message-ID: <20081114154848.GA21361@untroubled.org> (raw)
In-Reply-To: <20081114145914.GE25117@mit.edu>
[-- Attachment #1: Type: text/plain, Size: 800 bytes --]
On Fri, Nov 14, 2008 at 09:59:14AM -0500, Theodore Tso wrote:
> This is beginning to perhaps sound like a layout problem of some kind.
> How big is the filesystem that you are testing against?
The partition is almost 30GB.
> I'm guessing
> that if you have 725,000 small files, that it can't be much more than
> a gig or two, right?
The compressed stream itself expands to 4.4GB, and more on disk due to
block sizes.
> Can you send me the output of
>
> e2image -r /dev/XXX - | bzip2 ext4.e2i.bz2
>
> for both the ext4 and ext3 filesystems, after you have loaded them
> with your small files, and before you delete them?
Will do. Can you accept LZMA so I can save a bit of bandwidth?
--
Bruce Guenter <bruce@untroubled.org> http://untroubled.org/
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-11-14 15:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-13 18:57 ext4 unlink performance Bruce Guenter
2008-11-13 19:10 ` Bruce Guenter
2008-11-13 20:42 ` Theodore Tso
2008-11-14 4:11 ` Bruce Guenter
2008-11-14 14:59 ` Theodore Tso
2008-11-14 15:48 ` Bruce Guenter [this message]
2008-11-14 15:54 ` Theodore Tso
2008-11-15 20:44 ` Bruce Guenter
2008-11-15 23:08 ` Eric Sandeen
2008-11-16 0:56 ` Theodore Tso
2008-11-16 3:38 ` Bruce Guenter
2008-11-17 0:43 ` Andreas Dilger
[not found] ` <20081119024021.GA10185@mit.edu>
2008-11-19 18:10 ` Andreas Dilger
2008-11-19 21:18 ` Theodore Tso
2008-11-20 22:49 ` Bruce Guenter
2008-11-13 19:46 ` Theodore Tso
2008-11-13 20:27 ` Bruce Guenter
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=20081114154848.GA21361@untroubled.org \
--to=lists-linux-ext4@bruce-guenter.dyndns.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).