Loom's Next Phases
summary
Progress on virtual-thread pinning fixes lands in Loom Early Access builds and targets JDK 24; the fix lets a virtual thread unmount even inside synchronized methods so pinning is no longer a correctness hazard (one small performance niggle remains). Diagnostics added include a JSON thread dump with tens of thousands of threads parsable by tools, new JFR events, heap visibility, and a jcmd scheduler command that reports mounted/queued counts and allows dynamic target parallelism for containers. Workarounds include migrating hot sync code to ReentrantLock.
AI-written summary · about
chapters (7)
- 0:00Project Loom introduction
- 1:58Virtual thread adoption
- 3:55Handling pinning issues
- 7:16Replacing synchronization
- 9:02Testing Early Access builds
- 12:35JDK serviceability tools
- 15:26Monitoring and concurrency
related talks
47mThe Challenges of Introducing Virtual Threads to the Java Platform - Project Loom
46mLoom - Where Are We?
01h 00mLoom Virtual Threads in the JDK 20
51mWhat's Looming in Java The Why and What of Project Loom
57mUnveiling the Magical Power of Java Virtual Threads
47mConcurrent and Asynchronous Programming: Loom in Java 20 and 21
50mVirtual threads - no pain, no gain
02h 43mVirtual Threads, Structured Concurrency and Scoped Values in Java 25 and Beyond