linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rik van Riel <riel@conectiva.com.br>
To: Con Kolivas <conman@kolivas.net>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@digeo.com>
Subject: Re: [BENCHMARK] fork_load module tested for contest
Date: Wed, 25 Sep 2002 11:52:35 -0300 (BRT)	[thread overview]
Message-ID: <Pine.LNX.4.44L.0209251151220.22735-100000@imladris.surriel.com> (raw)
In-Reply-To: <1032964936.3d91cb48b1cca@kolivas.net>

On Thu, 26 Sep 2002, Con Kolivas wrote:

> I've been trialling a new load module for the contest benchmark
> (http://contest.kolivas.net) which simply forks a process that does
> nothing, waits for it to die, then repeats. Here are the results I have
> obtained so far:

> fork_load:
> Kernel                  Time            CPU             Ratio
> 2.4.19                  100.05          69%             1.37
> 2.4.19-ck7              74.65           95%             1.02
> 2.5.38                  77.35           95%             1.06
> 2.5.38-mm2              76.99           95%             1.06
>
> ck7 uses O1, preempt, low latency

Looks like the O(1) scheduler has a problem, then.  The continuous
fork() loop should get 20% of the CPU, not 5%.

regards,

Rik
-- 
Bravely reimplemented by the knights who say "NIH".

http://www.surriel.com/		http://distro.conectiva.com/

Spamtraps of the month:  september@surriel.com trac@trac.org


  reply	other threads:[~2002-09-25 14:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-25 14:42 [BENCHMARK] fork_load module tested for contest Con Kolivas
2002-09-25 14:52 ` Rik van Riel [this message]
2002-09-25 22:14 ` Cliff White
2002-09-25 23:07   ` Con Kolivas
2002-09-26  2:57 ` Useful fork info? WAS " Con Kolivas
2002-09-26  8:25   ` Ingo Molnar
2002-09-26 14:42     ` Rik van Riel
2002-09-26  8:36   ` William Lee Irwin III

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=Pine.LNX.4.44L.0209251151220.22735-100000@imladris.surriel.com \
    --to=riel@conectiva.com.br \
    --cc=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;
as well as URLs for NNTP newsgroup(s).