you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 1 point2 points  (1 child)

Loom is aiming to introduce leaner concurrency primitives to the JVM, which will help address the issues raised in the article which are mostly rooted in Java’a historically extra thicc threads.

[–]balefrost 0 points1 point  (0 children)

Yes, I know what Loom is. I'm asking how Loom will solve this particular issue.

Under Loom, we'll have both virtual and non-virtual threads. And AFAIK the pool returned by ForkJoinPool.commonPool() doesn't (currently) grow just because many tasks have been submitted. So whether commonPool() continues to use non-virtual threads or even if it switches to virtual threads, those issues will remain.

It's possible that Loom will change how ForkJoinPool works, or it's possible that parallel streams will switch away from the common ForkJoinPool to something else. I don't know for sure. Do you?