From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: Eric Sandeen <sandeen@redhat.com>
Cc: linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
Alan Piszcz <ap@solarrain.com>
Subject: Re: EXT4 is ~2X as slow as XFS (593MB/s vs 304MB/s) for writes?
Date: Sat, 27 Feb 2010 05:14:50 -0500 (EST) [thread overview]
Message-ID: <alpine.DEB.2.00.1002270513280.17433@p34.internal.lan> (raw)
In-Reply-To: <4B887548.50508@redhat.com>
On Fri, 26 Feb 2010, Eric Sandeen wrote:
> Eric Sandeen wrote:
>
> Oh, you need very recent util-linux-ng as well, and use libblkid from there
> with:
>
> [e2fsprogs] # ./configure --disable-libblkid
>
> Otherwise you can just feed mkfs.ext4 stripe & stride manually.
>
> -Eric
>
Hi,
Even when set, there is still poor performance:
http://busybox.net/~aldot/mkfs_stride.html
Raid Level: 0
Number of Physical Disks: 11
RAID chunk size (in KiB): 1024
number of filesystem blocks (in KiB)
mkfs.ext4 -b 4096 -E stride=256,stripe-width=2816
p63:~# /usr/bin/time mkfs.ext4 -b 4096 -E stride=256,stripe-width=2816 /dev/md0
mke2fs 1.41.10 (10-Feb-2009)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=256 blocks, Stripe width=2816 blocks
335765504 inodes, 1343055824 blocks
67152791 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=4294967296
40987 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
102400000, 214990848, 512000000, 550731776, 644972544
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 38 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
p63:~#
p63:~# mount /dev/md0 /r1 -o nobarrier,data=writeback
p63:/r1# dd if=/dev/zero of=file bs=1M count=10240
10240+0 records in
10240+0 records out
10737418240 bytes (11 GB) copied, 39.3674 s, 273 MB/s
p63:/r1#
Still very slow?
Let's try with some optimizations:
p63:/r1# mount /dev/md0 /r1 -o noatime,barrier=0,data=writeback,nobh,commit=100,nouser_xattr,nodelalloc,max_batch_time=0^C
Still not anywhere near 500-600MiB/s of XFS:
p63:/r1# dd if=/dev/zero of=file bs=1M count=10240
10240+0 records in
10240+0 records out
10737418240 bytes (11 GB) copied, 30.4824 s, 352 MB/s
p63:/r1#
Am I doing something wrong/is there a flag I am missing that will speed it
up? Or is this performance for sequential writes on EXT4?
Justin.
next prev parent reply other threads:[~2010-02-27 10:14 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-27 0:31 Justin Piszcz
2010-02-27 0:46 ` Dmitry Monakhov
2010-02-27 1:05 ` Justin Piszcz
2010-02-28 0:56 ` Asdo
2010-02-28 9:59 ` Justin Piszcz
2010-02-27 0:51 ` Eric Sandeen
2010-02-27 1:08 ` Justin Piszcz
2010-02-27 1:12 ` Eric Sandeen
2010-02-27 1:28 ` Eric Sandeen
2010-02-27 10:14 ` Justin Piszcz [this message]
2010-02-27 10:51 ` Justin Piszcz
2010-02-27 11:09 ` Justin Piszcz
2010-02-27 11:36 ` Justin Piszcz
2010-02-28 5:42 ` tytso
2010-02-28 14:55 ` Justin Piszcz
2010-03-01 8:39 ` Andreas Dilger
2010-03-01 9:21 ` Justin Piszcz
2010-03-01 14:48 ` Michael Tokarev
2010-03-01 15:07 ` Justin Piszcz
2010-03-01 16:15 ` Eric Sandeen
2010-02-28 23:50 ` Dave Chinner
2010-03-02 0:08 ` Eric Sandeen
2010-03-02 0:37 ` Eric Sandeen
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=alpine.DEB.2.00.1002270513280.17433@p34.internal.lan \
--to=jpiszcz@lucidpixels.com \
--cc=ap@solarrain.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®