public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jamie Lokier <jamie@shareable.org>
To: Eric <eric@cisu.net>
Cc: linux-kernel@vger.kernel.org, "Stephan T. Lavavej" <stl@nuwen.net>
Subject: Re: Process Creation Speed
Date: Mon, 19 Apr 2004 10:48:33 +0100	[thread overview]
Message-ID: <20040419094833.GB13007@mail.shareable.org> (raw)
In-Reply-To: <200404190043.04358.eric@cisu.net>

Eric wrote:
> > None of this answers the question which is relevant to linux-kernel:
> > why does process creation take 7.5ms and fail to scale with CPU
> > internal clock speed over a factor of 4 (600MHz x86 to 2.2GHz x86).
> 
> The reason it doesn't scale is probably because the kernel always runs at a 
> specified speed, 100HZ which leaves 10ms(i believe?) timeslices. I would try 
> a HZ patch and bump it up to 1000, i bet you would see a big difference then.

Hmm.  The timer speed shouldn't affect the measured speed of fork() at
all.  It might show up if the measuring program is dependent on the
timer in some way, though.

-- Jamie

  reply	other threads:[~2004-04-19  9:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-17  2:16 Process Creation Speed Stephan T. Lavavej
2004-04-18  5:44 ` Eric
2004-04-19  0:30   ` Jamie Lokier
2004-04-19  2:15     ` Eric
2004-04-19  3:04       ` Jamie Lokier
2004-04-19  5:43         ` Eric
2004-04-19  9:48           ` Jamie Lokier [this message]
2004-04-19 12:09             ` Johannes Stezenbach
2004-04-19 12:44               ` Stephan T. Lavavej
2004-04-19 22:48                 ` David Lang
2004-04-22 13:40                 ` Jakob Oestergaard
2004-04-19 13:28               ` Jamie Lokier
     [not found] <1MFUQ-1zo-3@gated-at.bofh.it>
     [not found] ` <1MGnU-1U9-19@gated-at.bofh.it>
2004-04-19 15:43   ` Andi Kleen

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=20040419094833.GB13007@mail.shareable.org \
    --to=jamie@shareable.org \
    --cc=eric@cisu.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stl@nuwen.net \
    /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