All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jose R. Santos" <jrs@us.ibm.com>
To: Jean-Pierre Dion <jean-pierre.dion@bull.net>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Ext4 benchmarks
Date: Wed, 28 Mar 2007 09:20:50 -0500	[thread overview]
Message-ID: <460A79C2.6030406@us.ibm.com> (raw)
In-Reply-To: <460A3010.6080201@bull.net>

Jean-Pierre Dion wrote:
> Hi Jose,
>
> thank you for the feedback.
>
> We took your remarks into account and we are doing some perfs with
> iozone (close to desktop activity, mono-thread) and ffsb (allows to run 
> benchs
> in a multi-thread activity like a server does, different blocks sizes...).
>
> We compare ext3 and ext4 (with extents, w/ and w/o del alloc...)...
>
> We will publish the results on bullopensource.org
>   

Hi Jean-Pierre,

While it may be to late for the purposes of your OLS paper, one thing 
that doesn't seem to be getting much attention is the performance of a 
file system while doing many meta-data operations or throughput testing 
during heavy journal log activity.  I believe that IOzone is very 
limited in testing this and FFSB isn't much better at it either.  
Eventually, I plan to add support in FFSB to create workload profile 
were one can select a weight balance of these types of operations.

Is this something that you are already doing for this round of testing?

-JRS

  parent reply	other threads:[~2007-03-28 14:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-20 15:20 Ext4 benchmarks Jean-Pierre Dion
2007-03-21  3:08 ` Jose R. Santos
2007-03-28  9:06   ` Jean-Pierre Dion
2007-03-28 11:27     ` Ric Wheeler
2007-04-02 14:55       ` Jean-Pierre Dion
2007-03-28 14:20     ` Jose R. Santos [this message]
2007-03-30  8:43       ` Johann Lombardi
2007-03-30 18:50         ` Andreas Dilger
2007-04-02 14:56       ` Jean-Pierre Dion
2007-04-04 17:06 ` Cordenner jean noel
2007-04-04 19:21   ` Andreas Dilger
2007-04-04 21:18     ` Mingming Cao
2007-04-04 22:40       ` ext4 patch queue update Mingming Cao

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=460A79C2.6030406@us.ibm.com \
    --to=jrs@us.ibm.com \
    --cc=jean-pierre.dion@bull.net \
    --cc=linux-ext4@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 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.