Path: ...!weretis.net!feeder8.news.weretis.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!raubtier-asyl.eternal-september.org!.POSTED!not-for-mail
From: Bonita Montero <Bonita.Montero@gmail.com>
Newsgroups: comp.lang.c++,comp.lang.c
Subject: Re: Threads across programming languages
Date: Fri, 3 May 2024 09:00:30 +0200
Organization: A noiseless patient Spider
Lines: 19
Message-ID: <v1222d$db4v$1@raubtier-asyl.eternal-september.org>
References: <GIL-20240429161553@ram.dialup.fu-berlin.de>
 <v0ogum$1rc5n$1@dont-email.me> <v0ovvl$1ur12$4@dont-email.me>
 <v0p06i$1uq6q$5@dont-email.me>
 <v0shti$2vrco$2@raubtier-asyl.eternal-september.org>
 <v0spsh$31ds4$3@dont-email.me>
 <v0stic$325kv$3@raubtier-asyl.eternal-september.org>
 <v0svtn$32o8h$1@dont-email.me>
 <v0t091$32qj6$1@raubtier-asyl.eternal-september.org>
 <v0u90h$3c1r5$4@dont-email.me> <v0v7rf$3lu04$1@dont-email.me>
 <v0v8u3$3m7rm$1@dont-email.me>
 <v0v9oh$3mcpv$1@raubtier-asyl.eternal-september.org>
 <v116s6$4at1$2@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Date: Fri, 03 May 2024 09:00:29 +0200 (CEST)
Injection-Info: raubtier-asyl.eternal-september.org; posting-host="c030ccadbcaefe746bb34fa5f5a5f34a";
	logging-data="437407"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1+Rxjr4umarqm6dQFiQusDql/9xQIaZ82Q="
User-Agent: Mozilla Thunderbird
Cancel-Lock: sha1:WURiQai/XmihWItEmcSouZX9l0A=
Content-Language: de-DE
In-Reply-To: <v116s6$4at1$2@dont-email.me>
Bytes: 2375

Am 03.05.2024 um 01:16 schrieb Lawrence D'Oliveiro:
> On Thu, 2 May 2024 07:53:21 +0200, Bonita Montero wrote:
> 
>> Am 02.05.2024 um 07:39 schrieb Lawrence D'Oliveiro:
>>
>>> Another reason to avoid threads. So long as your async tasks have an
> await
>>> call somewhere in their main loops, that should be sufficient to avoid
>>> most bottlenecks.
>>
>> If you have a stream of individual I/Os and the processing of the I/Os
>> takes more time than the time between the I/Os you need threads.
> 
> That makes the CPU the bottleneck. Which is not the case we’re discussing
> here.

No, the processing beetween the I/O can mostly depend on other I/Os,
which is the standard case for server applications.