From: Con Kolivas <kernel@kolivas.org>
To: Nick Piggin <piggin@cyberone.com.au>
Cc: linux kernel mailing list <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@digeo.com>
Subject: Re: [BENCHMARK] 2.5.65-mm2 with contest
Date: Thu, 20 Mar 2003 12:37:50 +1100 [thread overview]
Message-ID: <200303201237.50702.kernel@kolivas.org> (raw)
In-Reply-To: <3E791241.3070700@cyberone.com.au>
On Thu, 20 Mar 2003 11:58, Nick Piggin wrote:
> Con Kolivas wrote:
> >Contest results for mm2:
>
> Contest is starting to look good. Especially in
> loads and lcpu.
Very good point. Some of the loads are exhibiting better overall cpu usage and
dropping the compile time (tar loads are a good example)
> >no_load:
> >Kernel [runs] Time CPU% Loads LCPU% Ratio
> >2.5.65 3 80 95.0 0.0 0.0 1.00
> >2.5.65-mm1 3 79 94.9 0.0 0.0 1.00
> >2.5.65-mm2 3 79 94.9 0.0 0.0 1.00
>
> AS is now on par with deadline here which is nice.
Excellent.
> [snip]
>
> >dbench_load:
> >Kernel [runs] Time CPU% Loads LCPU% Ratio
> >2.5.65 3 542 14.2 9.0 62.5 6.78
> >2.5.65-mm1 3 361 21.1 6.3 55.4 4.57
> >2.5.65-mm2 3 437 17.4 7.7 60.6 5.53
>
> I don't know if this is a good balance shift or not. Maybe not
> related to AS but I'll investigate.
I dont think there are other tweaks in mm2 that could be responsible. It's
extremely hard to know what exactly is the best balance in this load. If
dbench 16 should get 80% of the total cpu usage (since the kernel compile has
4 processes) then mm2 is very close at 78%. However I didnt think dbench was
supposed to be a particularly cpu bound task. The overall cpu usage is higher
which is good though.
> Thanks Con
A pleasure,
Con
prev parent reply other threads:[~2003-03-20 1:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-19 23:16 [BENCHMARK] 2.5.65-mm2 with contest Con Kolivas
2003-03-20 0:58 ` Nick Piggin
2003-03-20 1:37 ` Con Kolivas [this message]
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=200303201237.50702.kernel@kolivas.org \
--to=kernel@kolivas.org \
--cc=akpm@digeo.com \
--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 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.