☕ If you liked this video and want to support my channel, please consider buying me a coffee. Your contribution helps me create more content like this: 👉 Buy Me a Coffee: www.buymeacoffee.com/andrey.fadeev 👉 Ko-fi: ko-fi.com/andreyfadeev Please also subscribe to my other resources: 👉 Substack: blog.andreyfadeev.com 👉 Telegram: t.me/andreyfadeevchannel I'm truly grateful for your support, and thank you for watching! 🙏
How exactly are the other threads terminated? Would, say, a plain infinite loop also be somehow interrupted if it's running in a virtual thread - something that wouldn't happen in a regular thread?
I don't think it happens really, a virtual thread with with `while true println` never exists even if the other thread finished with exception and the on failure policy :( So it still needs interruptible points in the cycle, eg sleep
It kinda does. Vthreads generally won't help you with CPU bound tasks. For that I'd still prefer fixed threadpool of platform threads or similar and let OS scheduler to control the preemption.
Probably the best way to look at the issue is, that vthreads are cheap to block (that means, cheap to wait for something to happen) and it's where they shine.
A virtual thread that does no blocking will never be interrupted. This is "optimal" but not always desired behavior - optimal in the sense that it is probably the most performant, not always desired because sometimes you want responsiveness over throughput. If you want to give a chance for other virtual threads to perform work a workaround is to call Thread.sleep. For some reason they didn't decide to let Thread.yield() to do this, which would be a great improvement.
☕ If you liked this video and want to support my channel, please consider buying me a coffee. Your contribution helps me create more content like this:
👉 Buy Me a Coffee: www.buymeacoffee.com/andrey.fadeev
👉 Ko-fi: ko-fi.com/andreyfadeev
Please also subscribe to my other resources:
👉 Substack: blog.andreyfadeev.com
👉 Telegram: t.me/andreyfadeevchannel
I'm truly grateful for your support, and thank you for watching! 🙏
How exactly are the other threads terminated? Would, say, a plain infinite loop also be somehow interrupted if it's running in a virtual thread - something that wouldn't happen in a regular thread?
I don't think it happens really, a virtual thread with with `while true println` never exists even if the other thread finished with exception and the on failure policy :(
So it still needs interruptible points in the cycle, eg sleep
Does it matter if your task is IO bound Vs CPU bound?
It kinda does. Vthreads generally won't help you with CPU bound tasks. For that I'd still prefer fixed threadpool of platform threads or similar and let OS scheduler to control the preemption.
Probably the best way to look at the issue is, that vthreads are cheap to block (that means, cheap to wait for something to happen) and it's where they shine.
yeap that's it :)
A virtual thread that does no blocking will never be interrupted. This is "optimal" but not always desired behavior - optimal in the sense that it is probably the most performant, not always desired because sometimes you want responsiveness over throughput.
If you want to give a chance for other virtual threads to perform work a workaround is to call Thread.sleep. For some reason they didn't decide to let Thread.yield() to do this, which would be a great improvement.
@@bobbycrosby9765 you can also call (Thread/.isInterrupted (Thread/currentThread))