From: Eric Sandeen <sandeen@redhat.com>
To: ext4 development <linux-ext4@vger.kernel.org>
Subject: delalloc is crippling fs_mark performance
Date: Fri, 18 Jul 2008 11:11:30 -0500 [thread overview]
Message-ID: <4880C0B2.9040706@redhat.com> (raw)
running fs_mark like this:
fs_mark -d /mnt/test -D 256 -n 100000 -t 4 -s 20480 -F -S 0
(256 subdirs, 100000 files/iteration, 4 threads, 20k files, no sync)
on a 1T fs, with and without delalloc (mount option), is pretty interesting:
http://people.redhat.com/esandeen/ext4/fs_mark.png
somehow delalloc is crushing performance here. I'm planning to wait
'til the fs is full and see what the effect is on fsck, and look at the
directory layout for differences compared to w/o delalloc.
But something seems to have gone awry here ...
This is on 2.6.26 with the patch queue applied up to stable.
-Eric
next reply other threads:[~2008-07-18 16:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-18 16:11 Eric Sandeen [this message]
2008-07-18 23:00 ` delalloc is crippling fs_mark performance Eric Sandeen
2008-07-19 15:44 ` Eric Sandeen
2008-07-19 17:20 ` Theodore Tso
2008-07-21 9:37 ` Aneesh Kumar K.V
2008-07-21 16:22 ` Eric Sandeen
2008-07-21 22:39 ` Andreas Dilger
2008-07-22 11:11 ` 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=4880C0B2.9040706@redhat.com \
--to=sandeen@redhat.com \
--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.