Loom and high performance networking

[Alan Bateman]

On 13/08/2024 16:34, robert engels wrote:
> I did. It didn’t make any difference. I checked the thread dump as well and the extras were created.
>
> Surprised that lowering the priority didn’t help - so now I need to think about other options. It feels like something when the carriers can use all the cores that the poller is prevented from running - like some sort of lock being held by the carrier/vt and do it thrashes around until it eventually gets a chance.
>
With pollerMode=2 then the the work is done on virtual threads so I 
assume you don't see the master poller stealing CPU cycles.

In any case, what you describe sounds a bit like bursty usage where all 
FJP workers are scanning for work before parking, and/or something else 
that may be macOS specific when running out of some resource. I suspect 
tuning the networking params to remove the errors/timeouts might make it 
a bit easier to study.

-Alan

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/loom-dev/attachments/20240814/64578ac2/attachment.htm>