From: Mingming Cao <cmm@us.ibm.com>
To: Alex Tomas <alex@clusterfs.com>
Cc: ext2-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [Ext2-devel] Re: [RFC] extents,delayed allocation,mballoc for ext3
Date: 14 Apr 2004 10:49:59 -0700 [thread overview]
Message-ID: <1081965005.15980.6906.camel@localhost.localdomain> (raw)
In-Reply-To: <m3ekqqoj3m.fsf@bzzz.home.net>
On Wed, 2004-04-14 at 05:10, Alex Tomas wrote:
>
> I've just benched ext3 vs. ext3+reservation vs. ext3+delalloc vs. xfs.
> it was tiobench.
> 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
>
Hi Alex,
Nice comparison! The ext3 reservation system use more cpus because we do
reservations in memory( not on disk) and we have a global lock per
filesystem to guard the operation. The current search for a new
reservation window algorithm is not perfect right now.
extents and delayed allocation probably is the right way to go for next
generation (maybe ext4). Currently I just try to fix the missing
preallocation feature in ext3, without break the disk compatibility and
involve too much changes....
Thanks for your interest.
Mingming
prev parent reply other threads:[~2004-04-14 17:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-13 19:28 [RFC] extents,delayed allocation,mballoc for ext3 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
2004-04-14 17:49 ` Mingming Cao [this message]
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=1081965005.15980.6906.camel@localhost.localdomain \
--to=cmm@us.ibm.com \
--cc=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