Re:Java Virtual Threads: A Case Study
by dikei on Wednesday July 17, 2024 @02:01AM
(#40983004)
> The problem with the naïve design is that even with virtual threads, you risk running out of (heap) memory if the threads ever block.
The key with virtual threads is they are so light weight that you can have thousands of them running concurrently: even when they block for I/O, it doesn't matter. It's similar to light weight coroutine in other language like Go or Kotlin.
The key with virtual threads is they are so light weight that you can have thousands of them running concurrently: even when they block for I/O, it doesn't matter. It's similar to light weight coroutine in other language like Go or Kotlin.