From: Con Kolivas <kernel@kolivas.org>
To: Andrew Morton <akpm@digeo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BENCHMARK] 2.5.63-mm2 + i/o schedulers with contest
Date: Wed, 5 Mar 2003 17:02:10 +1100 [thread overview]
Message-ID: <200303051702.10810.kernel@kolivas.org> (raw)
In-Reply-To: <20030304001032.034f60fa.akpm@digeo.com>
On Tue, 4 Mar 2003 07:10 pm, Andrew Morton wrote:
> 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.
Tried again - these were done as part of a full contest run, not just mem_load
by itself, but these were the mem_load results:
98
128
135
then it oopsed (the one I posted earlier) and wasn't really usable after that
point. Perhaps they're related. The mystery remains. I'll see what happens
next mm release.
Con
prev parent reply other threads:[~2003-03-05 5:51 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
2003-03-04 8:20 ` Con Kolivas
2003-03-05 6:02 ` 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=200303051702.10810.kernel@kolivas.org \
--to=kernel@kolivas.org \
--cc=akpm@digeo.com \
--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 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.