5 ms·
By the OS, not by the scheduler see https://cr.openjdk.java.net/~rpressler/loom/loom/sol1_part2.html#forced-preemption https://cr.openjdk.java.net/~rpressler/lo
by _old_dude_ 5y ago
By the OS, not by the scheduler
see https://cr.openjdk.java.net/~rpressler/loom/loom/sol1_part2.html#forced-preemption https://cr.openjdk.java.net/~rpressler/loom/loom/sol1_part2....
- vips7L 5y agoWhat about pron's comments here then? https://news.ycombinator.com/item?id=27885569 https://news.ycombinator.com/item?id=27885569 > Second, Loom's virtual threads can also be forcibly preempted by the scheduler at any safepoint to implement time sharing
- _old_dude_ 5y agoFor me, preemption by the Java scheduler is not currently supported but may be added in the future, after all the goroutine were not preempted at the beginning in Go. The whole quote > Second, Loom's virtual threads can also be forcibly preempted by the scheduler at any safepoint to implement time sharing. Currently, this capability isn't exposed because we're yet to find a use-case for it I believe it's a reference to [1] but i may be wrong. [1] https://download.java.net/java/early_access/loom/docs/api/java.base/java/lang/Continuation.html#tryPreempt(java.lang.Thread) https://download.java.net/java/early_access/loom/docs/api/ja...
- vips7L 5y ago> The whole quote Sorry I was skimming! Thanks!