From: Alex Tomas <bzzz.tomas@gmail.com>
To: Eric Sandeen <sandeen@redhat.com>
Cc: ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: More testing: 4x parallel 2G writes, sequential reads
Date: Thu, 08 Nov 2007 02:17:55 +0300 [thread overview]
Message-ID: <473247A3.5020800@gmail.com> (raw)
In-Reply-To: <47323F73.5080708@redhat.com>
Hi,
could you try to larger preallocation? like 512/1024/2048 blocks, please?
thanks, Alex
Eric Sandeen wrote:
> I tried ext4 vs. xfs doing 4 parallel 2G IO writes in 1M units to 4
> different subdirectories of the root of the filesystem:
>
> http://people.redhat.com/esandeen/seekwatcher/ext4_4_threads.png
> http://people.redhat.com/esandeen/seekwatcher/xfs_4_threads.png
> http://people.redhat.com/esandeen/seekwatcher/ext4_xfs_4_threads.png
>
> and then read them back sequentially:
>
> http://people.redhat.com/esandeen/seekwatcher/ext4_4_threads_read.png
> http://people.redhat.com/esandeen/seekwatcher/xfs_4_threads_read.png
> http://people.redhat.com/esandeen/seekwatcher/ext4_xfs_4_read_threads.png
>
> At the end of the write, ext4 had on the order of 400 extents/file, xfs
> had on the order of 30 extents/file. It's clear especially from the
> read graph that ext4 is interleaving the 4 files, in about 5M chunks on
> average. Throughput seems comparable between ext4 & xfs nonetheless.
>
> Again this was on a decent HW raid so seek penalties are probably not
> too bad.
>
> -Eric
> -
> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2007-11-07 23:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-07 22:42 More testing: 4x parallel 2G writes, sequential reads Eric Sandeen
2007-11-07 23:09 ` Andreas Dilger
2007-11-07 23:18 ` Eric Sandeen
2007-11-08 3:39 ` Eric Sandeen
2007-11-07 23:17 ` Alex Tomas [this message]
2007-11-08 0:14 ` Shapor Naghibzadeh
2007-11-08 3:06 ` 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=473247A3.5020800@gmail.com \
--to=bzzz.tomas@gmail.com \
--cc=linux-ext4@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 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.