All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: delalloc is crippling fs_mark performance
Date: Fri, 18 Jul 2008 18:00:12 -0500	[thread overview]
Message-ID: <4881207C.1040004@redhat.com> (raw)
In-Reply-To: <4880C0B2.9040706@redhat.com>

Eric Sandeen wrote:
> 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

I oprofiled both with and without delalloc for the first 15% of the fs fill:

==> delalloc.op <==
CPU: AMD64 processors, speed 2000 MHz (estimated)
Counted CPU_CLK_UNHALTED events (Cycles outside of halt state) with a
unit mask of 0x00 (No unit mask) count 100000
samples  %        image name               app name
symbol name
56094537 73.6320  ext4dev.ko               ext4dev
ext4_mb_use_preallocated
642479    0.8433  vmlinux                  vmlinux
__copy_user_nocache
523803    0.6876  vmlinux                  vmlinux                  memcmp
482874    0.6338  jbd2.ko                  jbd2
do_get_write_access
480687    0.6310  vmlinux                  vmlinux
kmem_cache_free
403604    0.5298  ext4dev.ko               ext4dev
str2hashbuf
400471    0.5257  vmlinux                  vmlinux
__find_get_block

==> nodelalloc.op <==
CPU: AMD64 processors, speed 2000 MHz (estimated)
Counted CPU_CLK_UNHALTED events (Cycles outside of halt state) with a
unit mask of 0x00 (No unit mask) count 100000
samples  %        image name               app name
symbol name
56167198 56.8949  ext4dev.ko               ext4dev
ext4_mb_use_preallocated
1524662   1.5444  jbd2.ko                  jbd2
do_get_write_access
1234776   1.2508  vmlinux                  vmlinux
__copy_user_nocache
1115267   1.1297  jbd2.ko                  jbd2
jbd2_journal_add_journal_head
1053102   1.0667  vmlinux                  vmlinux
__find_get_block
963646    0.9761  vmlinux                  vmlinux
kmem_cache_free
958804    0.9712  vmlinux                  vmlinux                  memcmp

not sure if this points to anything or not - but
ext4_mb_use_preallocated is working awfully hard in both cases :)

-Eric

  reply	other threads:[~2008-07-18 23:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-18 16:11 delalloc is crippling fs_mark performance Eric Sandeen
2008-07-18 23:00 ` Eric Sandeen [this message]
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=4881207C.1040004@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.