All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <mason@suse.com>
To: Michael Carmack <karmak@karmak.org>
Cc: reiserfs-list@namesys.com
Subject: Re: Benchmarks from Guru Labs
Date: 18 Jul 2002 08:24:25 -0400	[thread overview]
Message-ID: <1026995065.2486.5.camel@tiny> (raw)
In-Reply-To: <20020718115327.GE3841@ariel.karmak.org>

On Thu, 2002-07-18 at 07:53, Michael Carmack wrote:
> 
> I didn't see any mention of this in the archives. There are some
> ReiserFS benchmarks at
> 
>     http://www.gurulabs.com/ext3-reiserfs.html
> 
> The first set of tests (for small files) show a significant performance
> advantage with 'notail' turned on. Assuming disk space is not an issue,
> are there any performance advantages to 'notail' that are not reflected
> in these tests?

notail is faster in most cases.  With some tail tuning, tails could be
faster for synchronous applications (like mail servers) when the file
size is <= blocksize.  This is because flushing the tail to disk would
be free with flushing the new inode information.

> 
> Also, can anyone comment on why Ext3 has a significant edge over ReiserFS
> in the small-file tests, but the situation reverses as file-size 
> increases? There's not much commentary in the article.

Getting good consistent results out of postmark is tricky.  Notice that
between the 2nd and 3rd tests, he changed 3 different postmark variables
(file size, number of files, number of transactions).

What I can say is that we've been doing performance fixes for reiserfs
for a while now, and some of them are really coming together.  Many will
go into 2.4.20-pre.

-chris





  reply	other threads:[~2002-07-18 12:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-18 11:53 Benchmarks from Guru Labs Michael Carmack
2002-07-18 12:24 ` Chris Mason [this message]
     [not found]   ` <200207181342.19138.tdickenson@geminidataloggers.com>
2002-07-18 13:02     ` Chris Mason

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=1026995065.2486.5.camel@tiny \
    --to=mason@suse.com \
    --cc=karmak@karmak.org \
    --cc=reiserfs-list@namesys.com \
    /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.