From: William Lee Irwin III <wli@holomorphy.com>
To: Con Kolivas <conman@kolivas.net>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
Rik van Riel <riel@conectiva.com.br>
Subject: Re: Useful fork info? WAS Re: [BENCHMARK] fork_load module tested for contest
Date: Thu, 26 Sep 2002 01:36:10 -0700 [thread overview]
Message-ID: <20020926083610.GM3530@holomorphy.com> (raw)
In-Reply-To: <1033009036.3d92778cee9b9@kolivas.net>
On Thu, Sep 26, 2002 at 12:57:16PM +1000, Con Kolivas wrote:
> 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?
Well, it means something. I should point out that the cost of pagetable
copying is increased by pte-based reverse mapping, and your "children
forked" throughput results reflect this. It's a known issue, and AFAIK
regarded as a reasonable tradeoff.
Cheers,
Bill
prev parent reply other threads:[~2002-09-26 8:30 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
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 [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=20020926083610.GM3530@holomorphy.com \
--to=wli@holomorphy.com \
--cc=conman@kolivas.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=riel@conectiva.com.br \
/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.