mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: jogi@planetzork.ping.de
To: "Chris Mason" <mason@suse.com>
Cc: reiserfs-list@namesys.com, linux-kernel@vger.kernel.org,
	"Beau Kuiper" <kuib-kl@ljbc.wa.edu.au>
Subject: Re: [PATCH] reiserfs speedup for 2.4.9+
Date: 23 Sep 2001 15:28:41 +0200	[thread overview]
Message-ID: <20010923152841.A9671@planetzork.spacenet> (raw)
In-Reply-To: <1696760000.1001194777@tiny>
In-Reply-To: <1696760000.1001194777@tiny>; from mason@suse.com on Sat, Sep 22, 2001 at 05:39:37PM -0400

On Sat, Sep 22, 2001 at 05:39:37PM -0400, Chris Mason wrote:
> 
> Hello everyone,

Hello Chris,

> Beau pointed me towards a performance bug in reiserfs, where reiserfs_write_super would be called excessively.  
> 
> Turns out that 2.4.9 included some new super handling code that 
> interacted poorly with how reiserfs uses kupdated calls to 
> write_super to trigger writebacks of metadata.
> 
> This is most obvious with benchmarks like bonnie++, where 
> 2.4.9 and 2.4.10 reiserfs do very poorly.
> 
> This patch makes things much better in my tests, I'd appreciate 
> a few more testers.  The only risk is reiserfs using slightly 
> more memory, but only if I've screwed something up.

Just to share my two cents. First I have to tell that the skipping
of alsaplayer playing .wav files I experienced during kernel compiles
or other activities is almost completly gone. Furthermore I did some
performance testing of kernel compiles (actions that are done:
untar kernel, patch kernel, make -j50 bzImage modules, 5 times in a
row). These are the results of plain 2.4.10-pre14aa1:

Elapsed (wall clock) time (h:mm:ss or m:ss): 6:25.90
Elapsed (wall clock) time (h:mm:ss or m:ss): 6:15.43
Elapsed (wall clock) time (h:mm:ss or m:ss): 6:01.95
Elapsed (wall clock) time (h:mm:ss or m:ss): 6:12.56
Elapsed (wall clock) time (h:mm:ss or m:ss): 6:35.61

And here are the results of 2.4.10-pre14aa1 + your patch:

Elapsed (wall clock) time (h:mm:ss or m:ss): 5:23.55
Elapsed (wall clock) time (h:mm:ss or m:ss): 5:32.21
Elapsed (wall clock) time (h:mm:ss or m:ss): 5:34.77
Elapsed (wall clock) time (h:mm:ss or m:ss): 6:17.55
Elapsed (wall clock) time (h:mm:ss or m:ss): 5:49.31

Is the performance fix also required for 2.4.9-acXX ?

Regards,

   Jogi

-- 

Well, yeah ... I suppose there's no point in getting greedy, is there?

    << Calvin & Hobbes >>

  reply	other threads:[~2001-09-23 13:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-22 21:39 Chris Mason
2001-09-23 13:28 ` jogi [this message]
2001-09-23 22:38 ` 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=20010923152841.A9671@planetzork.spacenet \
    --to=jogi@planetzork.ping.de \
    --cc=kuib-kl@ljbc.wa.edu.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mason@suse.com \
    --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 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®