All of lore.kernel.org
 help / color / mirror / Atom feed
From: Till Immanuel Patzschke <tip@inw.de>
To: lse-tech <lse-tech@lists.sourceforge.net>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: 15000+ processes -- poor performance ?!
Date: Wed, 18 Dec 2002 16:53:45 -0800	[thread overview]
Message-ID: <3E011899.A3FBDAF1@inw.de> (raw)
In-Reply-To: 3E0116D6.35CA202A@inw.de

forgot the kernel version (2.4.20aa1)...

Till Immanuel Patzschke wrote:

> Dear List(s),
>
> as part of my project I need to run a very high number of processes/threads on a
> linux machine.  Right now I have a Dual-PIII 1.4G w/ 8GB RAM -- I am running
> 4000 processes w/ 2-3 threads each totaling in a process count of 15000+
> processes (since Linux doesn't really distinguish between threads and
> processes...).
> Once I pass the 10000 (+/-) pocesses load increases drastically (on startup,
> although it returns to normal), however the system time (on one processor)
> reaches for 54% (12061 procs) while the only non sleeping process is top -- the
> system is basically doing nothing (except scheduling the "nothing" which
> consumes significant system time).
> Is there anything I can do to reduce that system load/time?  (I haven't been
> able to exactly define the "line" but it definitly gets worse the more processes
> need to be handled.)
> Does any of the patchsets address this particular problem?
> BTW: The processes are all alike...
>
> Thanks for you help!
>
> Immanuel
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/


  parent reply	other threads:[~2002-12-19  0:45 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-19  0:46 15000+ processes -- poor performance ?! Till Immanuel Patzschke
2002-12-19  0:47 ` [Lse-tech] " Martin J. Bligh
2002-12-19  0:53 ` Till Immanuel Patzschke [this message]
2002-12-19  1:15   ` William Lee Irwin III
2002-12-19  1:12     ` David Lang
2002-12-19  1:25       ` William Lee Irwin III
2002-12-19  1:20         ` David Lang
2002-12-19  1:36           ` William Lee Irwin III
2002-12-19  1:42           ` Robert Love
2002-12-19  1:44             ` David Lang
2002-12-19  2:05               ` [Lse-tech] " William Lee Irwin III
2002-12-19 15:05                 ` Denis Vlasenko
2002-12-19 10:27                   ` William Lee Irwin III
2002-12-19 10:37                     ` Alex Tomas
2002-12-19 10:55                       ` William Lee Irwin III
2002-12-19 15:24                       ` Martin J. Bligh
2002-12-19 15:15                     ` Denis Vlasenko
2002-12-19  1:24     ` William Lee Irwin III
2002-12-19  0:59 ` Jeff Garzik
2002-12-19  1:11 ` William Lee Irwin III
2002-12-19 14:59 ` Denis Vlasenko
  -- strict thread matches above, loose matches on Subject: below --
2002-12-19  1:04 Perez-Gonzalez, Inaky
2002-12-19  1:13 ` Robert Love
2002-12-19  2:31 ` Alan Cox
2002-12-19  1:58   ` Rik van Riel
2002-12-19  2:01   ` 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=3E011899.A3FBDAF1@inw.de \
    --to=tip@inw.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lse-tech@lists.sourceforge.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 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.