Loom: Revolution or Implementation Detail?
summary
Project Loom introduces virtual threads and continuations-on-heap to the JVM so programs can create hundreds of thousands to millions of lightweight threads (demo: one million sleeping virtual threads) by multiplexing them onto a small number of carrier threads. It targets I/O-heavy workloads and lets traditional blocking APIs scale, but faces drawbacks: increased GC pressure from millions of continuation objects, no built-in preemption for CPU-bound tasks, and the need for careful use of blocking vs non-blocking APIs and resource limits.
AI-written summary · about
chapters (9)
- 0:00Loom in Java
- 7:47Virtual threads in Loom
- 11:22Continuation mechanism
- 18:04Carrier thread pool
- 26:23Virtual threads pros/cons
- 33:27Performance and GC impact
- 36:35Loom vs reactive
- 40:45Loom status and testing
- 42:54Summary and Q&A
related talks
01h 01mProject Loom: Revolution in Concurrency or Obscure Implementation Detail?
51mWhat's Looming in Java The Why and What of Project Loom
01h 13mProject 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
50mProject Loom: Helping Write Concurrent Applications on the Java Platform
47mThe Challenges of Introducing Virtual Threads to the Java Platform - Project Loom
39mProject Loom: Modern Scalable Concurrency for the Java Platform