public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: "Perez-Gonzalez, Inaky" <inaky.perez-gonzalez@intel.com>,
	"'Till Immanuel Patzschke'" <tip@inw.de>,
	lse-tech <lse-tech@lists.sourceforge.net>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 15000+ processes -- poor performance ?!
Date: Wed, 18 Dec 2002 18:01:47 -0800	[thread overview]
Message-ID: <20021219020147.GN31800@holomorphy.com> (raw)
In-Reply-To: <1040265088.27221.7.camel@irongate.swansea.linux.org.uk>

On Thu, 2002-12-19 at 01:04, Perez-Gonzalez, Inaky wrote:
>> If it has it ... well, I have no idea - maybe Robert Love would know.

On Thu, Dec 19, 2002 at 02:31:28AM +0000, Alan Cox wrote:
> He's running the -aa kernel, which has all the right bits for this too.
> In fact in some ways for very large memory boxes its probably the better
> variant

In my experience the most critical issues running 16K processes are:
(1) the highmem footprint of the pte's is significant
(2) the lowmem footprint of pmd's

and most of the rest is in the noise. It's probably a bad idea to run
top(1) or perhaps even mount /proc/ at all until top itself,
proc_pid_readdir(), and the tasklist_lock are all fixed.

Pretty much all he needs to "stay alive" is highpte of some flavor or
another. Performance etc. is addressed somewhat more by 2.5.x than -aa,
at least in the context of not degrading with this kind of multitasking.
i.e. shpte and pidhash. I've been randomly shooting down do_each_thread()
and for_each_process() loops in -wli, which is why I recommended it.

Bill

  parent reply	other threads:[~2002-12-19  1:55 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-19  1:04 15000+ processes -- poor performance ?! 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 [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-12-19  0:46 Till Immanuel Patzschke
2002-12-19  0:53 ` Till Immanuel Patzschke
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  0:59 ` Jeff Garzik
2002-12-19  1:11 ` William Lee Irwin III
2002-12-19 14:59 ` Denis Vlasenko

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=20021219020147.GN31800@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=inaky.perez-gonzalez@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lse-tech@lists.sourceforge.net \
    --cc=tip@inw.de \
    /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