What's Looming in Java The Why and What of Project Loom
summary
Project Loom adds JVM-managed virtual threads built on continuations that detach task state from OS threads so blocking IO no longer pins a thread. A demo replaces native threads that fail around ~7,500 with virtual threads that spawn up to 1,000,000 threads and still run, showing sleep/IO doesn’t hog carriers. Result: far denser concurrency, easier imperative exception handling and thread reuse; best for IO-bound, networked workloads, not CPU-bound parallelism.
AI-written summary · about
chapters (17)
- 0:00Introduction to Loom
- 0:48Concurrency vs Parallelism
- 2:16The Need for Asynchrony
- 3:35Java's History of Threads
- 5:49Thread Limitations
- 8:25Performance Realities
- 10:58Calculating Thread Count
- 13:27Horizontal Scaling
- 15:59The Cost of Multi-threading
- 18:29Thread Limitation Demo
- 21:52Rethinking the Paradigm
- 23:48Co-routines
- 25:15Continuations in Java
- 29:43Virtual Threads
- 32:37Virtual Thread Demo
- 37:15Non-blocking I/O
- 40:04Exception Handling and Conclusion
related talks
44mLoom: Revolution or Implementation Detail?
50mProject Loom: Helping Write Concurrent Applications on the Java Platform
47mThe Challenges of Introducing Virtual Threads to the Java Platform - Project Loom
01h 13mProject loom: Modern scalable concurrency for the Java platform
54mLooming in the cores
39mProject Loom: Modern Scalable Concurrency for the Java Platform
32mProject Loom? Better Futures? What’s next for JVM concurrent programming
01h 00mProject Loom? Better Futures? What’s next for JVM concurrent programming