Sujet : Re: Python recompile
De : chris.m.thomasson.1 (at) *nospam* gmail.com (Chris M. Thomasson)
Groupes : comp.lang.cDate : 11. Mar 2025, 22:12:01
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <vqq8v2$262gq$1@dont-email.me>
References : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31
User-Agent : Mozilla Thunderbird
On 3/10/2025 11:39 PM, Lawrence D'Oliveiro wrote:
On Mon, 10 Mar 2025 21:30:16 -0700, Chris M. Thomasson wrote:
On 3/10/2025 8:07 PM, Lawrence D'Oliveiro wrote:
>
On Mon, 10 Mar 2025 19:01:16 -0700, Chris M. Thomasson wrote:
>
On 3/10/2025 4:21 PM, Lawrence D'Oliveiro wrote:
On Mon, 10 Mar 2025 14:45:51 -0700, Chris M. Thomasson wrote:
>
On 3/10/2025 2:42 PM, Lawrence D'Oliveiro wrote:
>
It’s a blocking call:
>
This function associates a thread with the specified
completion port. A thread can be associated with at most one
completion port.
>
did you notice the timeout parameter?
>
That leads to busy-waiting.
>
It can be blocking ...
>
Yes, we already covered that.
>
So, that's that. There is no busy wait.
There is if you don’t want to block.
A "traditional" server loop would block on IOCP (aka INFINITE). However, trying to get IO completions can be useful in certain scenarios, (aka wait time zero). Also, waiting for say 5 minutes for IO and timing out so the server loop in the worker threads can examine other things can be beneficial as well. It's been a while since I have created server code.
Re: Python recompile
Re: Python recompile