From: David Lang <david.lang@digitalinsight.com>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Cc: "Nikita V. Youshchenko" <yoush@cs.msu.su>, linux-kernel@vger.kernel.org
Subject: Re: Local DoS (was: Strange 'zombie' problem both in 2.4 and 2.6)
Date: Mon, 14 Jun 2004 18:31:17 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.60.0406141754570.30956@dlang.diginsite.com> (raw)
In-Reply-To: <20040615002734.GA9801@logos.cnet>
On Mon, 14 Jun 2004, Marcelo Tosatti wrote:
> On Mon, Jun 14, 2004 at 10:01:53AM -0700, David Lang wrote:
>> I think I may be running into the same (or a similar) issue with a
>> workload that forks heavily (~3500 forks/sec). What can I do to let the
>> system survive this sort of load?
>
> Hi David,
>
> v2.6.7-mm tree contains a fix for this, adding a rlimit for
> pending signals.
I'll have to give this a try.
> Can you describe the problem you are seeing in more detail?
I have a stress-test I am running on a dual Opteron 1.4GHz box that
receives a network connection, forks a new process, does a little bit of
network traffic then the child exits. when I hammer this I get ~3500
connections/sec (with a significant amount of spare CPU, I'm limited by
my load boxes), but after a few secnds (8-10) something happens and the
parent stops receiving the sigchild signals. if I connect strace to the
parent process the signals are re-enabled and everything works for a
little bit longer before the process repeats.
if I only hit it with ~10,000 connections and then pause the box survives
indefinantly
running the same test on a dual athlonMP 2200+ I get ~2500 connections a
sec and it has no problems. I just compiled a 32 bit kernel for the
opteron and get ~3300 connections/sec (with no idle CPU time) and the box
doesn't lock up.
I don't know if this is becouse it's just below the threashold of the
problem or if there is a bug in the 64 bit kernel (or both)
I'm currently trying to tweak the 32 bit opteron kernel to get a smidge
more speed out of it to see if getting back up to the same speed starts
triggering the problem again.
David Lang
--
"Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it." - Brian W. Kernighan
prev parent reply other threads:[~2004-06-15 1:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-09 9:11 Nikita V. Youshchenko
2004-04-09 14:45 ` Denis Vlasenko
2004-04-13 13:10 ` Marcelo Tosatti
2004-06-14 17:01 ` David Lang
2004-06-15 0:27 ` Marcelo Tosatti
2004-06-15 1:31 ` David Lang [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=Pine.LNX.4.60.0406141754570.30956@dlang.diginsite.com \
--to=david.lang@digitalinsight.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
--cc=yoush@cs.msu.su \
/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
all inboxes | Powered by JetHome®