Concurrency options on the JVM
summary
Explains why JVM threads hit memory limits so blocking IO stops scale: running a 1k thread pool handles sleeps but pushing to ~3,000 threads triggers OOM, and limiting threads turns one-second work into three seconds idle. Compares approaches with concrete examples: Vert.x single-threaded event loop that does 10,000 sleeps in 1s but must avoid any blocking callbacks, actor pools like Akka and an alternative that compiles blocking code to lightweight Quasar fibers for many more concurrent tasks.
AI-written summary · about
chapters (6)
- 0:00Start
- 2:16What Is Concurrency
- 8:27Out of Memory Error
- 15:04Single Threaded Event Loop
- 25:50Quasar Framework
- 27:29Countdown Latches
related talks
41mIntroduction and pitfalls of Java's new concurrency model
31mJava Virtual Threads
01h 01mProject Loom: Revolution in Concurrency or Obscure Implementation Detail?
50mVirtual Threads, Structured Concurrency, Extent Locals: When to Use Them & How
34mIntroduction and pitfalls of Java's new concurrency model
58mCreating Asynchronous Applications with Virtual Threads
38mIntroduction and pitfalls of Java's new concurrency model
46mJava 21: The revolution of virtual threads - A Deep dive