Right, I’m not sure how loom is going to make any difference other than being able to resource limit certain groups of threads. The problem With virtual threads is pausing the thread during io; I’m not sure it is even possible to do.
The cool idea of virtual threads would be that I could make a bunch of threads share a single core which prevents a thread pool from locking up the entire system. This is one of the reasons why having 2x core processor threads can lead to a softirq attack locking up the system during very small message DOS. On Tue, May 19, 2020 at 11:14 AM Emmanuel Lécharny <elecha...@gmail.com> wrote: > > On 19/05/2020 16:01, Jonathan Valliere wrote: > > I’ll have to look at it but generally speaking virtual threads are not > for > > us because they cannot be paused during blocking operations within the > > kernel space so you can’t have ten virtual threads blocked on a kernel > > action on a single process thread. > > > > Java once had “green” threads back in version 3 or so but was removed and > > migrated to full threads. > > > Java 1.1. It was removed in 1.2. The reason is that even with green > threads, the JVM was running on one single thread, so performance wise, > it was just not an improvement, unless you had threads waiting for IOs. > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@mina.apache.org > For additional commands, e-mail: dev-h...@mina.apache.org > >
