From: Andreas Dilger <adilger@sun.com>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: tytso@mit.edu, Eric Sandeen <sandeen@redhat.com>,
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: Mon, 01 Mar 2010 01:39:18 -0700 [thread overview]
Message-ID: <832C6227-BF34-43C2-8768-1308C00AB17F@sun.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1002280628550.22822@p34.internal.lan>
On 2010-02-28, at 07:55, Justin Piszcz wrote:
> === CREATE RAID-0 WITH 11 DISKS
Have you tried testing with "nice" numbers of disks in your RAID set
(e.g. 8 disks for RAID-0, 9 for RAID-5, 10 for RAID-6)? The mballoc
code is really much better tuned for power-of-two sized allocations.
Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.
next prev parent reply other threads:[~2010-03-01 8:39 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-27 0:31 EXT4 is ~2X as slow as XFS (593MB/s vs 304MB/s) for writes? Justin Piszcz
2010-02-27 0:46 ` Dmitry Monakhov
2010-02-27 1:05 ` Justin Piszcz
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
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 [this message]
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=832C6227-BF34-43C2-8768-1308C00AB17F@sun.com \
--to=adilger@sun.com \
--cc=ap@solarrain.com \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sandeen@redhat.com \
--cc=tytso@mit.edu \
/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.