From: James Courtier-Dutton <James@superbug.co.uk>
To: Mateusz Berezecki <mateuszb@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6 context switching and posix threads performance question
Date: Mon, 29 Aug 2005 00:20:42 +0100 [thread overview]
Message-ID: <431246CA.4000500@superbug.co.uk> (raw)
In-Reply-To: <20050827121158.GA18406@oepkgtn.mshome.net>
Mateusz Berezecki wrote:
> Hello List Readers,
>
> I would really appreciate any comment on the overall performance of task
> switching with 25 000 threads running on the Linux system. I was asked to work
> on some software which spawns 25 000 threads and I am really worried if
> it will ever work on 2 CPU HP Blade. The kernel was modified to support
> bigger threads amount running (I have no idea how it was done, probably
> just changing hardcoded limits) What is the performance impact of
> so much threads on the overall system performance? Is there any ?
> Wouldn't it be that such application would spend all of its time
> switching contexts ? I'm asking for some kind of an authoritative answer
> quite urgently. What is the optimum thread amount on 2 CPU SMP system
> running Linux ?
>
>
> Thank you very much in advance
> Mateusz
>
You would get much better performance by switching the application to
use a thread pool using a fixed low number ( about CPU*2 = 4) of worker
threads.
James
next prev parent reply other threads:[~2005-08-28 23:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-27 12:11 Linux 2.6 context switching and posix threads performance question Mateusz Berezecki
2005-08-27 12:26 ` Peter Zijlstra
[not found] ` <aec8d6fc050827053047b1b667@mail.gmail.com>
2005-08-27 12:38 ` Peter Zijlstra
2005-08-27 12:58 ` Arjan van de Ven
2005-08-27 13:09 ` Con Kolivas
2005-08-27 14:43 ` Alan Cox
2005-08-28 23:20 ` James Courtier-Dutton [this message]
2005-08-30 17:46 ` Christoph Lameter
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=431246CA.4000500@superbug.co.uk \
--to=james@superbug.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mateuszb@gmail.com \
/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