public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <mason@suse.com>
To: Andreas Hartmann <andihartmann@freenet.de>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: Very poor performance with 2.6.4
Date: Mon, 29 Mar 2004 09:23:48 -0500	[thread overview]
Message-ID: <1080570227.20685.93.camel@watt.suse.com> (raw)
In-Reply-To: <4067BF2C.8050801@p3EE060D4.dip0.t-ipconnect.de>

On Mon, 2004-03-29 at 01:16, Andreas Hartmann wrote:
> Andrew Morton wrote:
> > Andreas Hartmann <andihartmann@freenet.de> wrote:
> >>
> >> I tested kernel 2.6.4. While compiling kdelibs and kdebase, I felt, that
> >>  kernel 2.6 seems to be slower than 2.4.25.
> >> 
> >>  So I did some tests to compare the performance directly. Therefore I
> >>  rebooted for everey test in init 2 (no X).
> >> 
> >>  I locally compiled 2.6.5rc2 3 times under 2.6.4 and under 2.4.25 on a
> >>  reiserfs LVM partition, which resides onto a IDE HD (using DMA) and got
> >>  the following result:
> >> 
> >>  In the middle, compiling under kernel 2.6.4 tooks 9.3% more real time than
> >>  under 2.4.25.
> >>  The user-processortime is about the same, but the system-processortime is
> >>  under 2.6.4 32.9% higher than under 2.4.25.
> > 
> > Try mounting your reiserfs filesystems with the `-o nolargeio=1' option.
> 
> This didn't help.
> 
> > 
> > If that doesn't help, please run a comparative kernel profile.  See
> > Documentation/basic_profiling.txt.
> 
> I'll do this next.

You might also want to try 2.6.5-rc2 which has a set of reiserfs fixes
from 2.4.x.  I'm hoping those will clean things up for you.

2.6.5-rc2-mm3 and higher have a number of other reiserfs performance
fixes, but most of those were not in 2.4.  Trying them out will
complicate the picture (although I'm still interested in numbers from
-mm).

-chris



  reply	other threads:[~2004-03-29 14:21 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-28 20:02 Very poor performance with 2.6.4 Andreas Hartmann
2004-03-28 20:24 ` Matt H.
2004-03-28 21:11 ` Sasa U
2004-03-29  4:07 ` Andrew Morton
2004-03-29  6:16   ` Andreas Hartmann
2004-03-29 14:23     ` Chris Mason [this message]
2004-03-29 19:35       ` Andreas Hartmann
2004-03-29 19:42       ` Andreas Hartmann
2004-04-02  8:19       ` Andreas Hartmann
2004-04-02 10:23         ` Andrew Morton
2004-04-02 20:53           ` Andreas Hartmann
2004-04-02 21:13             ` Andrew Morton
2004-04-03  0:23               ` Andreas Hartmann
2004-03-29 17:41   ` Andreas Hartmann
     [not found] <1EOM0-3oS-17@gated-at.bofh.it>
2004-03-28 22:47 ` Andi Kleen

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=1080570227.20685.93.camel@watt.suse.com \
    --to=mason@suse.com \
    --cc=akpm@osdl.org \
    --cc=andihartmann@freenet.de \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox