effectiveness of jdk.virtualThreadScheduler.maxPoolSize

[Alan Bateman]

On 09/01/2023 08:46, Arnaud Masson wrote:
>
> Side note : it seems “more” preemptive time sharing was added for 
> goroutines in Go 1.14 to avoid the kind of scheduling starvation we 
> discussed:
>
> https://medium.com/a-journey-with-go/go-asynchronous-preemption-b5194227371c
>
>

As I understand it, Go doesn't expose the equivalent of platform threads 
so that may have been a forced move.

For Project Loom, this is the "custom scheduler" topic where the 
primitive for forced preemption is the primitive required to do time 
sharing. It will take a bit of time to figure out if/how this might be 
exposed, and time will tell if we really this with the default scheduler.

-Alan







-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/loom-dev/attachments/20230109/c22dcc63/attachment-0001.htm>