From: Andrew Morton <akpm@digeo.com>
To: Con Kolivas <conman@kolivas.net>
Cc: linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [BENCHMARK] 2.5.40-mm2 with contest
Date: Mon, 07 Oct 2002 00:38:20 -0700 [thread overview]
Message-ID: <3DA139EC.8A34A593@digeo.com> (raw)
In-Reply-To: 1033960902.3da0fdc6839aa@kolivas.net
Con Kolivas wrote:
>
>
> Here are the latest results including 2.5.40-mm2 with contest v0.50
> (http://contest.kolivas.net)
>
> ...
>
> mem_load:
> Kernel [runs] Time CPU% Loads LCPU% Ratio
> 2.4.19 [3] 100.0 72 33 3 1.49
> 2.5.38 [3] 107.3 70 34 3 1.60
> 2.5.39 [2] 103.1 72 31 3 1.53
> 2.5.40 [2] 102.5 72 31 3 1.53
> 2.5.40-mm1 [2] 107.7 68 29 2 1.60
> 2.5.40-mm2 [2] 165.1 44 38 2 2.46
>
-mm2 has the "don't swap so much" knob. By default it is set at 50%.
The VM _wants_ to reclaim lots of memory from mem_load so that
gcc has some cache to chew on. But you the operator have said
"I know better and I don't want you to do that".
Because it is prevented from building enough cache, gcc is issuing
a ton of reads, which are hampering the swapstorm which is happening
at the other end of the disk. It's a lose-lose.
There's not much that can be done about that really (apart from
some heavy-handed load control) - if you want to optimise for
throughput above all else,
echo 100 > /proc/sys/vm/swappiness
(I suspect our swap performance right now is fairly poor, in terms
of block allocation, readaround, etc. Nobody has looked at that in
some time afaik. But tuning in there is unlikely to make a huge
difference).
next prev parent reply other threads:[~2002-10-07 7:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-07 3:21 [BENCHMARK] 2.5.40-mm2 with contest Con Kolivas
2002-10-07 7:38 ` Andrew Morton [this message]
2002-10-08 1:01 ` Con Kolivas
2002-10-08 1:25 ` Andrew Morton
2002-10-08 1:41 ` Con Kolivas
2002-10-10 17:40 ` Bill Davidsen
2002-10-10 23:17 ` Con Kolivas
2002-10-10 17:32 ` Bill Davidsen
2002-10-10 18:11 ` Andrew Morton
-- strict thread matches above, loose matches on Subject: below --
2002-10-07 12:11 Ed Tomlinson
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=3DA139EC.8A34A593@digeo.com \
--to=akpm@digeo.com \
--cc=conman@kolivas.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox