Alex Nedelcu on Nostr: Overheard… #Java actually had M:N scheduling on top of Solaris, black when on other ...
Overheard…
#Java actually had M:N scheduling on top of Solaris, black when on other OSs Java was single-threaded (N:1 scheduling).
What's new about #Java's virtual threads (Project Loom) is that Java now has both 1:1 scheduling and M:N scheduling.
M:N is a compromise and can have scheduling issues. For those cases, in Java you're free to keep using platform threads directly. And from the programmer's perspective, there is no difference, as it's the same API. You're free to pick your poison.
#Java actually had M:N scheduling on top of Solaris, black when on other OSs Java was single-threaded (N:1 scheduling).
What's new about #Java's virtual threads (Project Loom) is that Java now has both 1:1 scheduling and M:N scheduling.
M:N is a compromise and can have scheduling issues. For those cases, in Java you're free to keep using platform threads directly. And from the programmer's perspective, there is no difference, as it's the same API. You're free to pick your poison.