mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Linux Portal" <linportal@gmail.com>
To: "Theodore Tso" <tytso@mit.edu>,
	"Linux Portal" <linportal@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: First benchmarks of the ext4 file system
Date: Mon, 23 Oct 2006 17:32:21 +0200	[thread overview]
Message-ID: <ceccffee0610230832l4eb76b0dvd1c4c275ae462d3d@mail.gmail.com> (raw)
In-Reply-To: <20061023020731.GA486@thunk.org>

On 10/23/06, Theodore Tso <tytso@mit.edu> wrote:
> On Sun, Oct 22, 2006 at 01:57:36AM +0200, Linux Portal wrote:
> > ext4 is 20 percent faster writer than ext3 or reiser4, probably thanks
> > to extents and delayed allocation. On other tests it is either
> > slightly faster or slightly slower. reiser4 comes as a nice surprise,
> > winning few benchmarks. Both are very stable, no errors during
> > testing.
>
> As Andrew has already pointed out, we don't have delayed allocation
> merged in into the -mm tree yet.

OK.

> If you have the
> time/energy/interest, a very useful thing that would very much help
> the filesystem developers of all filesystems to do would be to
> automated your tesitng enough that you can do these tests on a
> frequent basis, both to track regressions caused by changes in other
> parts of the kernel, as well we to see what happens as various bits of
> functionality get added to the filesystem.  This of course can become
> an arbitrarily a huge amount of work, as you add more filesystems and
> benchmarks, but it's the sort of thing which is incredibly useful
> especially if the hardware is held constant across a large number of
> filesystems, workloads/benchmarks, and kernel versions.
>

I agree completely. That was my original idea, to prepare some setup for
thorough testing, but I soon discovered that would really be a huge project,
because of so many parameters involved.

So, at this time, I just satisfied my curiosity ;) with few simple tests of the
early version of ext4. We'll see what the future brings (how much free
time, in the first place ;)).

Best regards,

  reply	other threads:[~2006-10-23 15:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-21 23:57 Linux Portal
2006-10-22  0:45 ` Alistair John Strachan
2006-10-22  6:49 ` Andrew Morton
2006-10-22 12:42   ` Linux Portal
2006-10-23  2:07 ` Theodore Tso
2006-10-23 15:32   ` Linux Portal [this message]
2006-10-30  2:37     ` Bill Davidsen

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=ceccffee0610230832l4eb76b0dvd1c4c275ae462d3d@mail.gmail.com \
    --to=linportal@gmail.com \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®