Path: ...!2.eu.feeder.erje.net!3.eu.feeder.erje.net!feeder.erje.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com>
Newsgroups: comp.lang.c++,comp.lang.c
Subject: Re: Threads across programming languages
Date: Fri, 3 May 2024 20:09:10 -0700
Organization: A noiseless patient Spider
Lines: 39
Message-ID: <v148sm$10e4o$2@dont-email.me>
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>
 <v0v28q$3ku1r$1@raubtier-asyl.eternal-september.org>
 <v1176k$4at1$3@dont-email.me>
 <v12175$d305$2@raubtier-asyl.eternal-september.org>
 <v146qn$vrsv$8@dont-email.me> <v148kv$10e4o$1@dont-email.me>
 <v148pp$10e58$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Date: Sat, 04 May 2024 05:09:11 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="00566bb81b0a3452542610785f934900";
	logging-data="1063064"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX19myaVtasldMG4qanzMwz0y7e8c7KUvP9Q="
User-Agent: Mozilla Thunderbird
Cancel-Lock: sha1:XwUGOnz3ohzZaDD6Gviuz832kY8=
In-Reply-To: <v148pp$10e58$1@dont-email.me>
Content-Language: en-US
Bytes: 3294

On 5/3/2024 8:07 PM, Chris M. Thomasson wrote:
> On 5/3/2024 8:05 PM, Chris M. Thomasson wrote:
>> On 5/3/2024 7:33 PM, Lawrence D'Oliveiro wrote:
>>> On Fri, 3 May 2024 08:45:58 +0200, Bonita Montero wrote:
>>>
>>>> Am 03.05.2024 um 01:21 schrieb Lawrence D'Oliveiro:
>>>>
>>>>> I/O performance certainly is possible with Python, and it has the 
>>>>> high-
>>>>> performance production-quality frameworks to prove it.
>>>>
>>>> I thought about high performance code with >= 1e5 IOs/s.
>>>> That's not possible with Python.
>>>
>>> Sure it is. Try the “stress_test” script I wrote here
>>> <https://gitlab.com/ldo/inotipy_examples>. It can easily generate 
>>> more I/O
>>> events than the Linux kernel can cope with, on whatever machine 
>>> you’re on.
>>
>> Ahh the stress test. Record moments, especially right when the server 
>> dies from running out of resources. Record that moment. Restart the 
>> test... Set a limit a little lower than the one that killed the system 
>> before... See if it dies again... If so, repeat until it does not die. 
>> Then record this number for the system.
>>
>> [...]
>>
> 
> This process should be done during the installation of the new server 
> software... :^)
> 
> The server says install now, or run stress tests, if you check here, we 
> will try to crash your system, but reboot with a lower number and keep 
> trying until we see no crash... This number is the death point of the 
> tests wrt the system... ;^D ROFL!!!

I actually wrote server tests that did exactly that back on the good ol 
winnt 4.0. lol!