From: Andreas Hartmann <andihartmann@freenet.de>
To: Chris Mason <mason@suse.com>
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 21:35:42 +0200 [thread overview]
Message-ID: <40687A8E.5000604@pC19F1BE6.dip0.t-ipconnect.de> (raw)
In-Reply-To: <1080570227.20685.93.camel@watt.suse.com>
Chris Mason wrote:
> 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.
Ok, here is the result for 2.6.5-rc2 (3 times middle, with preemption),
compared to 2.4.25.
The result is, the performancedifference to 2.4.25 is the same as for
2.6.4 as described above.
Nearly means: The real processing time is about 1% faster than under
2.6.4, but 8.3% slower than with 2.4.25. The system-processortime is 1.2%
faster than under 2.6.4 but 31,7% more than under 2.4.25. The times for
the user-processortime is unchanged.
But I'm not shure if these values are really significant, because the
values for the real time meassured each try differ a lot under 2.6.
For example 2.6.5rc2:
between 9.07 min and 8.37 min for real time.
Under 2.4.25, the differences are a lot of smaller: between 8.06 min and
8.15 min for real time.
The values for user and system time are nearly constant with 6.49 min and
36 sec (kernel 2.6) and 6.43 min / 27 sec for 2.4.25.
Regards,
Andreas Hartmann
next prev parent reply other threads:[~2004-03-29 19:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-28 20:02 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
2004-03-29 19:35 ` Andreas Hartmann [this message]
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=40687A8E.5000604@pC19F1BE6.dip0.t-ipconnect.de \
--to=andihartmann@freenet.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mason@suse.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®