From: Goswin von Brederlow <goswin-v-b@web.de>
To: Theodore Tso <tytso@MIT.EDU>
Cc: Szabolcs Szakacsits <szaka@ntfs-3g.org>, linux-ext4@vger.kernel.org
Subject: Re: Porting Zfs features to ext2/3
Date: Thu, 07 Aug 2008 14:09:35 +0200 [thread overview]
Message-ID: <877iat6n7k.fsf@frosties.localdomain> (raw)
In-Reply-To: <20080730012909.GC29748@mit.edu> (Theodore Tso's message of "Tue, 29 Jul 2008 21:29:09 -0400")
Theodore Tso <tytso@MIT.EDU> writes:
> On Tue, Jul 29, 2008 at 10:52:26PM +0000, Szabolcs Szakacsits wrote:
>> I did also an in memory test on a T9300@2.5, with disk I/O completely
>> eliminated. Results:
>>
>> tmpfs: 975 MB/sec
>> ntfs-3g: 889 MB/sec (note, this FUSE driver is not optimized yet)
>> ext3: 675 MB/sec
...
> So it's issueing lots of 4k writes, one page at a time, because it
> needs to track the completion of each block. This creates a
> significant CPU overhead, which dominates in an all-memory test.
> Although this is not an issue in real-life today, it will likely
> become an issue in real-life solid state disks (SSD's).
This already is a major issue for us. We are starting to use SAS raid boxes
that deliver >350MB/s write and >600MB/s read performance with lustre,
which is ext3 with patches. It is somewhat between ext3 and ext4 in
that it has some of its features but not all.
> Fortunately, ext4's blktrace when copying a large file looks like
> this:
That is promising. Once the 64BIT feature becomes usable we plan to
port lustre to use ext4 as base filesystem. The current 8TiB limit is
a real pain.
MfG
Goswin
next prev parent reply other threads:[~2008-08-07 12:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-27 8:49 Porting Zfs features to ext2/3 postrishi
2008-07-27 22:49 ` Theodore Tso
2008-07-27 22:49 ` Shehjar Tikoo
2008-07-27 23:37 ` Theodore Tso
2008-07-28 3:42 ` Shehjar Tikoo
2008-07-27 22:54 ` Eric Anopolsky
2008-07-27 23:38 ` Theodore Tso
2008-07-28 4:15 ` Eric Anopolsky
2008-07-28 12:40 ` Theodore Tso
2008-07-29 3:58 ` Eric Anopolsky
2008-07-29 16:46 ` Ric Wheeler
2008-07-30 6:00 ` Eric Anopolsky
2008-07-29 21:00 ` Szabolcs Szakacsits
2008-07-29 22:52 ` Szabolcs Szakacsits
2008-07-30 1:29 ` Theodore Tso
2008-08-07 12:09 ` Goswin von Brederlow [this message]
2008-07-30 1:34 ` Theodore Tso
2008-07-31 0:50 ` Szabolcs Szakacsits
2008-08-04 20:38 ` Szabolcs Szakacsits
2008-08-07 12:01 ` Goswin von Brederlow
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=877iat6n7k.fsf@frosties.localdomain \
--to=goswin-v-b@web.de \
--cc=linux-ext4@vger.kernel.org \
--cc=szaka@ntfs-3g.org \
--cc=tytso@MIT.EDU \
/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