From: Andrew Morton <akpm@digeo.com>
To: Robert Love <rml@tech9.net>
Cc: Con Kolivas <conman@kolivas.net>,
linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [BENCHMARK] 2.5.46-mm1 with contest
Date: Thu, 07 Nov 2002 15:58:48 -0800 [thread overview]
Message-ID: <3DCAFE38.16DED3BF@digeo.com> (raw)
In-Reply-To: 1036712891.764.2055.camel@phantasy
Robert Love wrote:
>
> On Thu, 2002-11-07 at 17:53, Con Kolivas wrote:
>
> > io_load:
> > Kernel [runs] Time CPU% Loads LCPU% Ratio
> > 2.5.44-mm6 [3] 284.1 28 20 10 3.98
> > 2.5.46 [1] 600.5 13 48 12 8.41
> > 2.5.46-mm1 [5] 134.3 58 6 8 1.88
> >
> > Big change here. IO load is usually the one we feel the most.
>
> Nice.
Mysterious.
> > Unfortunately I've only run this with preempt enabled so far and I believe
> > many of the improvements are showing this effect.
>
> Since your aim is desktop performance, I would like it if you always ran
> with kernel preemption enabled. That is what we are targeting for
> desktop performance.
I'd be interested in average-of-five runs both with and without
preemption.
Preemption seemed to do odd things to process_load as well. gcc gained
10% and the "load" lost 40%. But the %LCPU fell only 25%, which is
probably dodgy accounting. I wonder what's up with all that.
next prev parent reply other threads:[~2002-11-07 23:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-07 22:53 [BENCHMARK] 2.5.46-mm1 with contest Con Kolivas
2002-11-07 23:48 ` Robert Love
2002-11-07 23:58 ` Andrew Morton [this message]
2002-11-08 0:04 ` Robert Love
2002-11-08 6:04 ` Con Kolivas
2002-11-08 0:10 ` Benjamin LaHaise
-- strict thread matches above, loose matches on Subject: below --
2002-11-08 0:32 Alan Willis
2002-11-08 0:48 ` Andrew Morton
2002-11-08 21:08 ` Alan Willis
2002-11-08 21:21 ` Andrew Morton
[not found] ` <YWxhbg==.a11f3fbc6d68c50c7f190513c1d3bacf@1037045821.cotse.net>
2002-11-11 21:03 ` Andrew Morton
2002-11-11 21:11 ` Alan Willis
2002-11-11 21:32 ` Andrew Morton
2002-11-13 0:14 ` Denis Vlasenko
2002-11-12 20:07 ` Alan Willis
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=3DCAFE38.16DED3BF@digeo.com \
--to=akpm@digeo.com \
--cc=conman@kolivas.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@tech9.net \
/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.