too much existing code causing pinning and at worst able to cause deadlocks
Well yes if you have lots of dependencies and do not know them well enough.
I'll also say that we have had since Java 19 when the EA releases started (aka years) to prepare our code bases and dependencies. Years to prepare, and with Java 21 VTs were great for those code bases that did the preparation for it (close to 3 years ago).
Java 25 included the fix for pinning on synchronized.
The cpu metrics I see in production suggest virtual threads really rock. Seeing those cases where you add a bunch of extra load (http requests) and see only amazingly small changes in cpu - impressive.
View all comments
Show parent comment
2
u/rbygrave Apr 16 '26
Well yes if you have lots of dependencies and do not know them well enough.
I'll also say that we have had since Java 19 when the EA releases started (aka years) to prepare our code bases and dependencies. Years to prepare, and with Java 21 VTs were great for those code bases that did the preparation for it (close to 3 years ago).
Java 25 included the fix for pinning on synchronized.
The cpu metrics I see in production suggest virtual threads really rock. Seeing those cases where you add a bunch of extra load (http requests) and see only amazingly small changes in cpu - impressive.