The next phase of Project Loom and Virtual Threads
summary
Project Loom adds virtual threads that can scale to “million plus” per JVM, but existing object monitors cause pinning that blocks carrier threads and hurts scalability; a JEP 491 rewrite of monitors (early‑access builds, aiming for JDK 24) removes that need. Diagnostics expand (JFR pinned events, JSON thread dumps, heap dumps with unmounted stacks). New preview API uses a structured task scope with join policies (shutdown‑on‑failure, no Futures) to simplify concurrency and cancellation.
AI-written summary · about
chapters (7)
- 0:00Introduction to project Loom
- 6:32Understanding pinning issues
- 14:07Roadmap to resolve pinning
- 18:45Troubleshooting and tooling
- 26:43Structured concurrency overview
- 39:36Structured task scope API
- 50:29Conclusion and Q&A
related talks
47mThe Challenges of Introducing Virtual Threads to the Java Platform - Project Loom
46mLoom - Where Are We?
50mProject Loom: Helping Write Concurrent Applications on the Java Platform
51mWhat's Looming in Java The Why and What of Project Loom
01h 13mProject loom: Modern scalable concurrency for the Java platform
39mProject Loom: Modern Scalable Concurrency for the Java Platform
44mLoom: Revolution or Implementation Detail?
32mProject Loom? Better Futures? What’s next for JVM concurrent programming