From: Alex Tomas <alex@clusterfs.com>
To: <ext2-devel@lists.sourceforge.net>
Cc: linux-kernel@vger.kernel.org, <alex@clusterfs.com>
Subject: Re: [RFC] extents,delayed allocation,mballoc for ext3
Date: Wed, 14 Apr 2004 16:10:53 +0400 [thread overview]
Message-ID: <m3ekqqoj3m.fsf@bzzz.home.net> (raw)
In-Reply-To: <m365c3pthi.fsf@bzzz.home.net> (alex@clusterfs.com's message of "Tue, 13 Apr 2004 23:28:57 +0400")
I've just benched ext3 vs. ext3+reservation vs. ext3+delalloc vs. xfs.
it was tiobench.
Sequential Writes
File Blk Num Avg CPU
Identifier Size Size Thr Rate (CPU%) Latency Eff
---------------------------- ------ ----- --- ------ ------ --------- -----
ext3 1024 4096 4 13.34 14.76% 0.897 90
ext3-dalloc 1024 4096 4 26.39 19.26% 0.452 137
ext3-reserv 1024 4096 4 23.77 28.99% 0.529 82
xfs 1024 4096 4 27.22 20.68% 0.373 132
ext3 1024 4096 8 9.71 10.82% 2.421 90
ext3-dalloc 1024 4096 8 25.81 18.64% 0.816 138
ext3-reserv 1024 4096 8 23.62 29.49% 1.006 80
xfs 1024 4096 8 27.06 22.49% 0.763 120
ext3 1024 4096 16 6.60 7.891% 7.222 84
ext3-dalloc 1024 4096 16 24.99 19.71% 1.783 127
ext3-reserv 1024 4096 16 23.04 28.15% 1.849 82
xfs 1024 4096 16 24.84 20.58% 1.300 121
ext3 1024 4096 32 8.12 9.872% 8.111 82
ext3-dalloc 1024 4096 32 24.83 20.01% 2.995 124
ext3-reserv 1024 4096 32 22.72 29.51% 3.282 77
xfs 1024 4096 32 25.47 21.75% 2.247 117
ext3-dalloc is ext3 + extents + delayed allocation + multiblock allocator
ext3-reserv is ext3 + reservation patches by Mingming Cao
next prev parent reply other threads:[~2004-04-14 12:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-13 19:28 alex
2004-04-14 4:01 ` Matt Mackall
2004-04-14 12:05 ` Alex Tomas
2004-04-19 19:47 ` [Ext2-devel] " Stephen C. Tweedie
2004-04-20 22:05 ` Matt Mackall
2004-04-14 12:10 ` Alex Tomas [this message]
2004-04-14 17:49 ` Mingming Cao
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=m3ekqqoj3m.fsf@bzzz.home.net \
--to=alex@clusterfs.com \
--cc=ext2-devel@lists.sourceforge.net \
--cc=linux-kernel@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 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®