From: Andrew Morton <akpm@osdl.org>
To: Andreas Hartmann <andihartmann@freenet.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Very poor performance with 2.6.4
Date: Sun, 28 Mar 2004 20:07:10 -0800 [thread overview]
Message-ID: <20040328200710.66a4ae1a.akpm@osdl.org> (raw)
In-Reply-To: <40672F39.5040702@p3EE062D5.dip0.t-ipconnect.de>
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.
If that doesn't help, please run a comparative kernel profile. See
Documentation/basic_profiling.txt.
Thanks.
next prev parent reply other threads:[~2004-03-29 4:07 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 [this message]
2004-03-29 6:16 ` Andreas Hartmann
2004-03-29 14:23 ` Chris Mason
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=20040328200710.66a4ae1a.akpm@osdl.org \
--to=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 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.