From: Eric Sandeen <sandeen@redhat.com>
To: Eric Sandeen <sandeen@redhat.com>,
ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: More testing: 4x parallel 2G writes, sequential reads
Date: Wed, 07 Nov 2007 17:18:31 -0600 [thread overview]
Message-ID: <473247C7.4020101@redhat.com> (raw)
In-Reply-To: <20071107230905.GQ3966@webber.adilger.int>
Andreas Dilger wrote:
> The question is what the "best" result is for this kind of workload?
> In HPC applications the common case is that you will also have the data
> files read back in parallel instead of serially.
Agreed, I'm not trying to argue what's better or worse, I'm just seeing
what it's doing.
The main reason I did sequential reads back is that it more clearly
shows the file layout for each file on the graph. :) I'm just getting
a handle on how the allocations are going for various types of writes.
> The test shows ext4 finishing marginally faster in the write case, and
> marginally slower in the read case. What happens if you have 4 parallel
> readers?
I'll test that a bit later (have to run now); I expect parallel readers
may go faster, since the blocks are interleaved, and it might be able to
suck them up pretty much in order across all 4 files.
I'd also like to test some of this under a single head, rather than on
HW raid...
-Eric
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 [this message]
2007-11-08 3:39 ` Eric Sandeen
2007-11-07 23:17 ` Alex Tomas
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=473247C7.4020101@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.