From: Philip Martin <philip@codematters.co.uk>
To: Nick Piggin <piggin@cyberone.com.au>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.1 slower than 2.4, smp/scsi/sw-raid/reiserfs
Date: Thu, 05 Feb 2004 14:27:03 +0000 [thread overview]
Message-ID: <874qu5fvpk.fsf@codematters.co.uk> (raw)
In-Reply-To: <4021AF52.1080009@cyberone.com.au> (Nick Piggin's message of "Thu, 05 Feb 2004 13:49:54 +1100")
Nick Piggin <piggin@cyberone.com.au> writes:
> Sorry, I mean what is it that you are timing?
It's a bit of software (Subversion) built using "make -j4". It
consists of a little over 200 C files compiled to object code, then
linked to about a dozen shared libraries, and finally linked to create
over a dozen executables. It uses libtool, so each compile/link
involves running a bit of shell code before runing gcc. It lends
itself to parallel builds, on 2.4 there is little difference in the
build time using -j2, -j4, -j8. The source code is about 16MB and the
object/library/executable about 28MB.
>>This is the profile for 2.6.2, it is very much like 2.6.1
>>
>>248.07user 118.81system 3:42.00elapsed 165%CPU (0avgtext+0avgdata 0maxresident)k
>>0inputs+0outputs (434major+3770493minor)pagefaults 0swaps
>
> If you get time, could you test the patch I sent you?
Your patch doesn't apply to plain 2.6.2. I got 2.6.2-mm1 and it looks
like that already includes your patch, correct? This is what I got
for 2.6.2-mm1
247.02user 118.33system 3:51.24elapsed 157%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (176major+3771994minor)pagefaults 0swaps
so it's not really an improvement on plain 2.6.2.
--
Philip Martin
next prev parent reply other threads:[~2004-02-05 14:39 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-01 21:34 2.6.1 slower than 2.4, smp/scsi/sw-raid/reiserfs Philip Martin
2004-02-01 23:11 ` Andrew Morton
2004-02-01 23:42 ` Philip Martin
2004-02-01 23:52 ` Nick Piggin
2004-02-02 0:51 ` Philip Martin
2004-02-02 5:15 ` Nick Piggin
2004-02-02 8:58 ` Nick Piggin
2004-02-02 18:36 ` Philip Martin
2004-02-02 23:36 ` Nick Piggin
2004-02-02 23:49 ` Andrew Morton
2004-02-03 1:01 ` Philip Martin
2004-02-03 3:02 ` Nick Piggin
2004-02-03 16:44 ` Philip Martin
2004-02-03 0:34 ` Philip Martin
2004-02-03 3:52 ` Nick Piggin
2004-02-02 18:08 ` Philip Martin
2004-02-03 3:46 ` Andrew Morton
2004-02-03 16:46 ` Philip Martin
2004-02-03 21:29 ` Andrew Morton
2004-02-03 21:53 ` Philip Martin
2004-02-04 5:48 ` Nick Piggin
2004-02-04 17:50 ` Philip Martin
2004-02-04 23:38 ` Philip Martin
2004-02-05 2:49 ` Nick Piggin
2004-02-05 14:27 ` Philip Martin [this message]
2004-02-14 0:10 ` Philip Martin
-- strict thread matches above, loose matches on Subject: below --
2004-02-03 6:55 Samium Gromoff
2004-02-03 7:07 ` Andrew Morton
2004-02-03 7:52 ` Samium Gromoff
2004-02-03 7:57 ` Nick Piggin
2004-02-03 15:58 ` Valdis.Kletnieks
2004-02-03 7:13 ` Nick Piggin
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=874qu5fvpk.fsf@codematters.co.uk \
--to=philip@codematters.co.uk \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=piggin@cyberone.com.au \
/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