linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Con Kolivas <conman@kolivas.net>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@elte.hu>, Rik van Riel <riel@conectiva.com.br>
Subject: Useful fork info? WAS Re: [BENCHMARK] fork_load module tested for contest
Date: Thu, 26 Sep 2002 12:57:16 +1000	[thread overview]
Message-ID: <1033009036.3d92778cee9b9@kolivas.net> (raw)
In-Reply-To: <1032964936.3d91cb48b1cca@kolivas.net>

Quoting Con Kolivas <conman@kolivas.net>:

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

[...fresh results below...]

> ck7 uses O1, preempt, low latency
> Preempt=N for all other kernels
> 
> Clearly you can see the 2.5 kernels have a substantial lead over the
> current
> stable kernel.
> 
> This load module is not part of the contest package yet. I could certainly
> change it to fork n processes but I'm not really sure just how many n should
> be.


I have extra information from the trial of this module:

noload:
Kernel                  Time            CPU             Ratio
2.4.19                  72.90           99%             1.00
2.4.19-ck7              71.55           100%            0.98
2.5.38                  73.86           99%             1.01
2.5.38-mm2              73.93           99%             1.01

fork_load:
Kernel                  Time            CPU             Ratio
2.4.19                  97.11           67%             1.33
2.4.19-ck7              72.34           92%             0.99
2.5.38                  75.32           92%             1.03
2.5.38-mm2              74.99           92%             1.03

2.4.19: Children forked: 32750
2.4.19-ck7: Children forked: 6477
2.5.38: Children forked: 5545
2.5.38-mm2: Children forked: 5351

You can see clearly repeatedly forking a new process significantly slows down
compile time for 2.4.19 but not the O(1) based kernels. However, the number of
processes that are forked is significantly reduced.

Is this information useful? 

Con

  parent reply	other threads:[~2002-09-26  2:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-25 14:42 Con Kolivas
2002-09-25 14:52 ` Rik van Riel
2002-09-25 22:14 ` Cliff White
2002-09-25 23:07   ` Con Kolivas
2002-09-26  2:57 ` Con Kolivas [this message]
2002-09-26  8:25   ` Useful fork info? WAS " 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=1033009036.3d92778cee9b9@kolivas.net \
    --to=conman@kolivas.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=riel@conectiva.com.br \
    --subject='Useful fork info? WAS Re: [BENCHMARK] fork_load module tested for contest' \
    /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

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).