Project Loom: Helping Write Concurrent Applications on the Java Platform
summary
Project Loom adds virtual threads to the JDK implemented in Java on top of VM continuations, multiplexing millions of lightweight threads onto a few kernel threads; prototype shows stacks that grow/shrink, per-thread footprint in the hundreds of bytes and task switches well under a microsecond. Synchronous socket I/O is reimplemented in Java, structured APIs for structured concurrency and scope locals manage cancellation, deadlines and thread-local alternatives; native blocking and synchronized monitors remain limitations.
AI-written summary · about
chapters (11)
- 0:00Introduction to Project Loom
- 0:39The problem with threads
- 4:23Virtual threads solution
- 7:17Implementing virtual threads
- 10:53Structured concurrency
- 15:10Scopes and task management
- 20:54Scope locals vs thread locals
- 27:22Advanced thread customization
- 29:58Under the hood: continuations
- 36:38Current status and limitations
- 41:48Q&A and final thoughts
related talks
39mProject Loom: Modern Scalable Concurrency for the Java Platform
01h 13mProject loom: Modern scalable concurrency for the Java platform
51mWhat's Looming in Java The Why and What of Project Loom
32mProject Loom? Better Futures? What’s next for JVM concurrent programming
01h 00mProject Loom? Better Futures? What’s next for JVM concurrent programming
47mThe Challenges of Introducing Virtual Threads to the Java Platform - Project Loom
42mProject Loom Update
47mConcurrent and Asynchronous Programming: Loom in Java 20 and 21