Hi All - Use link below for my popular Java courses. Virtual Threads - www.mudraservices.com/udemycoupon.html?course=vthread Java Generics - www.mudraservices.com/udemycoupon.html?course=jgen For more of my courses, check out - www.mudraservices.com
Any thread pool of platform threads will limit concurrency because the total number of users in the Application cannot exceed beyond the maximum number of threads allowed in the pool. In IO bound apps, in most cases CPU utilization is still very low when it reaches the max limit. Virtual threads has no upper limit for threads (no thread pool) and so it allows the app to reach full CPU utilization.
Yes .. Thread locals work in the same Manner - whether platform or virtual Threads. For virtual threads, thread locals will Be preserved across platform threads for the same Virtual Thread
Depends .. if you are using reactive stack for scalability purposes then it’s easier to just use virtual threads than reactive stacks. There are some streaming use cases which may require reactive stacks
Hi All - Use link below for my popular Java courses.
Virtual Threads - www.mudraservices.com/udemycoupon.html?course=vthread
Java Generics - www.mudraservices.com/udemycoupon.html?course=jgen
For more of my courses, check out - www.mudraservices.com
Amazing. I am bringing on table discussion in architect meeting next time. We badly need this. Thanks a lot.
I am happy you enjoyed the video
One of the best, if not the best explanations I’ve received so far.
Glad it was helpful!
what a little gem channel i just discovered!! great vid. subscribed!
I am glad you enjoyed ! More to come
I really enjoyed this video. Excellent presentation. Thank you
Glad you liked it !
Wonderful explanation Viraj Sir!
I am glad you enjoyed it
Thank you for your valuable content 🙏
You are welcome !
Really really great explanation.
Glad you enjoyed!
Wonderful Explanation!
Glad you liked it
Nice video. How is it better than cached thread pool in Java?
Any thread pool of platform threads will limit concurrency because the total number of users in the Application cannot exceed beyond the maximum number of threads allowed in the pool. In IO bound apps, in most cases CPU utilization is still very low when it reaches the max limit. Virtual threads has no upper limit for threads (no thread pool) and so it allows the app to reach full CPU utilization.
Wonderful explanation 😃
Glad you think so!
What happens to threadlocal in virtual threads ? Is it persisted between the platform threads ?
Yes .. Thread locals work in the same
Manner - whether platform or virtual
Threads. For virtual threads, thread locals will Be preserved across platform threads for the same
Virtual Thread
Thank you!
You're welcome!
Thanks!
Glad you enjoyed !
Does it mean we dont need Completable future from now onwards or reactive stackl for most of the enterprices?
Depends .. if you are using reactive stack for scalability purposes then it’s easier to just use virtual threads than reactive stacks. There are some streaming use cases which may require reactive stacks
Once structured concurrency classes are out of preview, it would be easier to use that than completable futures