From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00
	autolearn=unavailable autolearn_force=no version=3.4.4
Path: 
 eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!mx02.eternal-september.org!.POSTED!not-for-mail
From: Simon Wright <simon@pushface.org>
Newsgroups: comp.lang.ada
Subject: Re: Structure of the multitasking server
Date: Sun, 15 Mar 2015 08:35:10 +0000
Organization: A noiseless patient Spider
Message-ID: <ly7fuiacap.fsf@pushface.org>
References: 
 <8b4d1170-22e6-40d3-8ed1-096dc0163491@m36g2000hse.googlegroups.com>
	<ho90bg.gnt.ln@hunter.axlog.fr>
	<71b51c8e-6bed-4156-9f52-31bef57b8575@googlegroups.com>
	<871tktuc9i.fsf@adaheads.sparre-andersen.dk>
	<bf5e1244-c5cb-475b-8555-de190aae4ae8@googlegroups.com>
	<uu0on2a375l0.1lixh9dqxrbh5.dlg@40tude.net>
	<c943b1fd-8c0c-4c22-ba8c-fb72fbd52805@googlegroups.com>
	<yyzfuq7j9nz5.5avuby2cb4u5.dlg@40tude.net>
	<a52cfca8-d276-47b1-bae3-b7fb572a9ffd@googlegroups.com>
Mime-Version: 1.0
Content-Type: text/plain
Injection-Info: mx02.eternal-september.org;
 posting-host="c266ac6a7b23adb6fddc6455356f7788";
	logging-data="482"; mail-complaints-to="abuse@eternal-september.org";
	posting-account="U2FsdGVkX19lRD48AAyCvrTaxQXB4eO4y2k/L60PCEM="
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.4 (darwin)
Cancel-Lock: sha1:Btx78RDI5KcQ2JvuQyQfPvGDixI=
	sha1:GxtrA0BWHjs/y2Trmxn3K7pnO1M=
Xref: news.eternal-september.org comp.lang.ada:25174
Date: 2015-03-15T08:35:10+00:00
List-Id: <comp.lang.ada>

gautier_niouzes@hotmail.com writes:

> There is 100% load in my case. 8 worker tasks, 8 CPUs, all busy with
> the number crunching. What I'm doing is running computation jobs in
> parallel on different tasks and ensuring all tasks are busy. Each time
> a worker is done, it gets quickly a new job and I'm happy.

I know this isn't closely related, but make has the flag -j (--jobs), which
specifies the number of jobs to run simultaneously. --jobs=4 was OK
(this is a Macbook Pro with an Intel Core i5), but building GCC with
just --jobs (run as many jobs simultaneously as possible) froze the
machine to the point where a forced power cycle was the only option. I
wasn't happy.