All of lore.kernel.org
 help / color / mirror / Atom feed
From: Theodore Tso <tytso@MIT.EDU>
To: Szabolcs Szakacsits <szaka@ntfs-3g.org>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Porting Zfs features to ext2/3
Date: Tue, 29 Jul 2008 21:34:27 -0400	[thread overview]
Message-ID: <20080730013427.GD29748@mit.edu> (raw)
In-Reply-To: <loom.20080729T222131-137@post.gmane.org>

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

Am I write in guessing that this test involved copying a single large
file, with no seeks?  What happens if you try benchmarking unpacking a
kernel source tar.bz2 file?  My guess is that ntfs-3g won't look as
good.  :-)

						- Ted

  parent reply	other threads:[~2008-07-30  1:35 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
2008-07-30  1:34       ` Theodore Tso [this message]
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=20080730013427.GD29748@mit.edu \
    --to=tytso@mit.edu \
    --cc=linux-ext4@vger.kernel.org \
    --cc=szaka@ntfs-3g.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.