From: Andrew Morton <akpm@digeo.com>
To: Con Kolivas <kernel@kolivas.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BENCHMARK] 2.5.63-mm2 + i/o schedulers with contest
Date: Tue, 4 Mar 2003 00:10:32 -0800 [thread overview]
Message-ID: <20030304001032.034f60fa.akpm@digeo.com> (raw)
In-Reply-To: <200303041354.03428.kernel@kolivas.org>
Con Kolivas <kernel@kolivas.org> wrote:
>
> Mem_load result of AS being slower was just plain weird with the result rising
> from 100 to 150 during testing.
>
Maybe we should just swap computers or something?
Finished compiling kernel: elapsed: 145 user: 180 system: 18
Finished mem_load: elapsed: 146 user: 0 system: 2 loads: 5000
Finished compiling kernel: elapsed: 135 user: 181 system: 17
Finished mem_load: elapsed: 136 user: 0 system: 2 loads: 4800
Finished compiling kernel: elapsed: 129 user: 181 system: 17
Finished mem_load: elapsed: 130 user: 0 system: 2 loads: 4800
256MB, dual CPU, ext3/IDE.
Whereas 2.5.63+bk gives:
Finished compiling kernel: elapsed: 131 user: 182 system: 17
Finished mem_load: elapsed: 131 user: 0 system: 1 loads: 4900
Finished compiling kernel: elapsed: 135 user: 182 system: 17
Finished mem_load: elapsed: 135 user: 0 system: 1 loads: 4800
Finished compiling kernel: elapsed: 129 user: 182 system: 17
Finished mem_load: elapsed: 129 user: 0 system: 1 loads: 4600
Conceivably swap fragmentation, but unlikely. Is it still doing a swapoff
between runs?
next prev parent reply other threads:[~2003-03-04 7:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-04 2:54 [BENCHMARK] 2.5.63-mm2 + i/o schedulers with contest Con Kolivas
2003-03-04 4:18 ` Nick Piggin
2003-03-04 5:15 ` Con Kolivas
2003-03-04 5:26 ` Nick Piggin
2003-03-04 5:29 ` Con Kolivas
2003-03-04 8:10 ` Andrew Morton [this message]
2003-03-04 8:20 ` Con Kolivas
2003-03-05 6:02 ` Con Kolivas
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=20030304001032.034f60fa.akpm@digeo.com \
--to=akpm@digeo.com \
--cc=kernel@kolivas.org \
--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;
as well as URLs for NNTP newsgroup(s).