From: Ray Fucillo <fucillo@intersystems.com>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: Hugh Dickins <hugh@veritas.com>,
Linus Torvalds <torvalds@osdl.org>,
Rik van Riel <riel@redhat.com>, Andi Kleen <ak@suse.de>,
Andrew Morton <akpm@osdl.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: process creation time increases linearly with shmem
Date: Mon, 29 Aug 2005 19:33:54 -0400 [thread overview]
Message-ID: <43139B62.7010502@intersystems.com> (raw)
In-Reply-To: <43115E67.1050305@yahoo.com.au>
Nick Piggin wrote:
> How does the following look? (I changed the comment a bit). Andrew, please
> apply if nobody objects.
Nick, I applied this latest patch to a 2.6.12 kernel and found that it
does resolve the problem. Prior to the patch on this machine, I was
seeing about 23ms spent in fork for ever 100MB of shared memory segment.
After applying the patch, fork is taking about 1ms regardless of the
shared memory size.
Many thanks to everyone for your help on this.
FWIW, an interesting side effect of this occurs when I run the database
with this patch internally on a Linux server that uses NIS. Its an
unrelated problem and not a kernel problem. Its due to the children
calling initgroups()... apparently when you have many processes making
simultaneous initgroups() calls something starts imposing very long
waits in increments of 3 seconds, so some processes return from
initgroups() in a few ms and other processes complete in 3, 6, 9, up to
21 seconds (plus a few ms). I'm not sure what the story is with that,
though its clearly not a kernel issue. If someone happens to have the
answer or a suggestion, great, otherwise I'll persue that elsewhere as
necessary. (I can reproduce this by simply adding a call to
initgroups() call in the child of the forktest program that I sent earlier)
next prev parent reply other threads:[~2005-08-29 23:34 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-24 18:43 process creation time increases linearly with shmem Ray Fucillo
2005-08-25 0:14 ` Nick Piggin
2005-08-25 13:07 ` Ray Fucillo
2005-08-25 13:13 ` Andi Kleen
2005-08-25 14:28 ` Nick Piggin
2005-08-25 17:31 ` Rik van Riel
2005-08-26 1:26 ` Nick Piggin
2005-08-26 1:50 ` Rik van Riel
2005-08-26 3:56 ` Linus Torvalds
2005-08-26 11:49 ` Hugh Dickins
2005-08-26 14:26 ` Nick Piggin
2005-08-26 17:00 ` Ray Fucillo
2005-08-26 17:53 ` Rik van Riel
2005-08-26 18:20 ` Ross Biro
2005-08-26 18:56 ` Hugh Dickins
[not found] ` <8783be660508260915524e2b1e@mail.gmail.com>
2005-08-26 16:38 ` Hugh Dickins
2005-08-26 16:43 ` Ross Biro
2005-08-26 18:07 ` Linus Torvalds
2005-08-26 18:41 ` Hugh Dickins
2005-08-26 22:55 ` Linus Torvalds
2005-08-26 23:10 ` Rik van Riel
2005-08-26 23:23 ` Linus Torvalds
2005-08-27 15:05 ` Nick Piggin
2005-08-28 4:26 ` Hugh Dickins
2005-08-28 6:49 ` Nick Piggin
2005-08-29 23:33 ` Ray Fucillo [this message]
2005-08-30 0:29 ` Nick Piggin
2005-08-30 1:03 ` Linus Torvalds
2005-08-30 0:34 ` Linus Torvalds
2005-08-25 14:05 Parag Warudkar
2005-08-25 14:22 ` Andi Kleen
2005-08-25 14:35 ` Nick Piggin
2005-08-25 14:47 ` Parag Warudkar
2005-08-25 15:56 ` Andi Kleen
2005-12-14 14:07 Brice Oliver
2005-12-14 16:21 ` Hugh Dickins
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=43139B62.7010502@intersystems.com \
--to=fucillo@intersystems.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
--cc=riel@redhat.com \
--cc=torvalds@osdl.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).