Project Loom Update
summary
Project Loom adds lightweight user threads (fibers) to the JVM by building fibers from continuations + scheduler that run on a smaller set of OS carrier threads, with the current prototype already supporting tens of millions of fibers in principle. Implemented pieces include blocking-friendly java.net and java.nio changes, fiber scopes for structured concurrency with cooperative cancellation and deadlines, and a thread-object inflation shim to preserve legacy APIs. Remaining problems: can't yield while holding a monitor (native-frame and monitor limitations), methodhandle migration, and ongoing performance tuning (lazy-copy, generated freeze code, processor-local experiments).
AI-written summary · about
chapters (8)
- 0:00Start
- 2:01How Are Fibers Implemented
- 11:24Structure Concurrency
- 29:41Debugger Support
- 31:44Conformation Freezing
- 32:43Lazy Copy
- 35:00Freezing the Objects
- 41:33Next Steps
related talks
43mProject Loom: Fibers and Continuations for the Java Virtual Machine
36mProject Loom
29mUntangled: Sneak peek at Project Loom
50mProject Loom: Helping Write Concurrent Applications on the Java Platform
53mFruits of the Loom – Lightweight Concurrency For the Java Platform
32mProject Loom? Better Futures? What’s next for JVM concurrent programming
35mUntangled: Sneak peek at Project Loom
01h 13mProject loom: Modern scalable concurrency for the Java platform
