On 2020-04-07 20:44, ToddAndMargo via perl6-users wrote:
On 2020-04-07 20:39, Paul Procacci wrote:
What happens when you try it?
What impact do you observe?
My guess is the impact is exactly the time it takes for your cpu to
perform the initial context switch for the syscall, and then another
when waking up.
Hi Paul,
I opened the resource monitor and watched the CPU load:
raku -e "say 'start sleep 10'; sleep 10; say 'stop sleep;'"
start sleep 10
stop sleep;
Nothing. Sleep must be recovering using a system interrupt.
Yippee!
-T
This is what I was afraid of. The old fashioned batch
programming wait 10 seconds:
>ping -n 10 -i 10 8.8.8.8
