LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: sfaibish <sfaibish@emc.com>
To: "Jan Engelhardt" <jengelh@linux01.gwdg.de>,
"Andi Kleen" <andi@firstfloor.org>
Cc: "Juan Piernas Canovas" <piernas@ditec.um.es>,
"kernel list" <linux-kernel@vger.kernel.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: Re: [ANNOUNCE] DualFS: File System with Meta-data and Data Separation
Date: Thu, 15 Feb 2007 20:43:23 -0500 [thread overview]
Message-ID: <op.tnti2lseunckof@usensfaibisl2e.eng.emc.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0702152044450.17168@yvahk01.tjqt.qr>
On Thu, 15 Feb 2007 14:46:34 -0500, Jan Engelhardt
<jengelh@linux01.gwdg.de> wrote:
>
> On Feb 15 2007 21:38, Andi Kleen wrote:
>>
>> Also I would expect your design to be slow for metadata read intensive
>> workloads. E.g. have you tried to boot a root partition with dual fs?
>> That's a very important IO benchmark for desktop Linux systems.
>
> Did someone say metadata intensive? Try kernel tarballs, they're a
> perfect workload. Tons of directories, and even more files here and
> there. Works wonders.
I just did now per your request. To make things more relevant I
created a file structure from the 2.4.19 kernel sources and repeated it
recursively into the deepest dir level (10) 4 times ending up with
7280 directories with 40 levels of directories depth and 1 GB
data set size. I run both tar and untar operations on the tree
for ext3, reiserfs, jfs and DualFS. I remounted the FS before
each test. I end up with 7280 directories 40 levels depth and
1 GB data. Both tar file and directory tree were on the FS under
test.
Here are the results - elapse time in sec:
tar untar
ext3: 144 143
reiserfs: 100 100
JFS: 196 140
DualFS: 63 54
Hope this helps.
>
>
> Jan
/Sorin
--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
next prev parent reply other threads:[~2007-02-16 1:43 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <op.tnkdlbgsrwwil4@brcsmondepl2c.corp.emc.com>
2007-02-14 21:10 ` sfaibish
2007-02-14 21:57 ` Jan Engelhardt
2007-02-15 18:38 ` Juan Piernas Canovas
2007-02-15 20:09 ` Jörn Engel
2007-02-15 22:59 ` Juan Piernas Canovas
2007-02-16 9:13 ` Jörn Engel
2007-02-16 11:05 ` Benny Amorsen
2007-02-16 23:47 ` Bill Davidsen
2007-02-17 15:11 ` Jörn Engel
2007-02-17 18:10 ` Bill Davidsen
2007-02-17 18:36 ` Jörn Engel
2007-02-17 20:47 ` Sorin Faibish
2007-02-18 5:59 ` Jörn Engel
2007-02-18 12:46 ` Jörn Engel
2007-02-19 23:57 ` Juan Piernas Canovas
2007-02-20 0:10 ` Bron Gondwana
2007-02-20 0:30 ` Jörn Engel
2007-02-21 4:36 ` Juan Piernas Canovas
2007-02-21 12:37 ` Jörn Engel
2007-02-21 18:31 ` Juan Piernas Canovas
2007-02-21 19:25 ` Jörn Engel
2007-02-22 4:30 ` Juan Piernas Canovas
2007-02-22 16:25 ` Jörn Engel
2007-02-22 19:57 ` Juan Piernas Canovas
2007-02-23 13:26 ` Jörn Engel
2007-02-24 22:35 ` Sorin Faibish
2007-02-25 2:41 ` Juan Piernas Canovas
2007-02-25 12:01 ` Jörn Engel
2007-02-26 3:48 ` Juan Piernas Canovas
2007-02-20 20:43 ` Bill Davidsen
2007-02-15 20:38 ` Andi Kleen
2007-02-15 19:46 ` Jan Engelhardt
2007-02-16 1:43 ` sfaibish [this message]
2007-02-15 21:09 ` Juan Piernas Canovas
2007-02-15 23:57 ` Andi Kleen
2007-02-16 4:57 ` Juan Piernas Canovas
2007-02-26 11:49 ` Yakov Lerner
2007-02-26 13:08 ` Matthias Schniedermeyer
2007-02-26 13:24 ` Sorin Faibish
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=op.tnti2lseunckof@usensfaibisl2e.eng.emc.com \
--to=sfaibish@emc.com \
--cc=andi@firstfloor.org \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=piernas@ditec.um.es \
--subject='Re: [ANNOUNCE] DualFS: File System with Meta-data and Data Separation' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).