#jdk21 — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #jdk21, aggregated by home.social.
-
100k blocking tasks. A few seconds. On a laptop. With #VirtualThreads in #Java25, that’s reality. Mihaela Gheorghe-Roman explains what changed since #JDK21 & why thread-per-request is back. Still running huge thread pools?
Rethink: https://javapro.io/2026/03/05/java-25-and-the-new-age-of-performance-virtual-threads-and-beyond/
-
100k blocking tasks. A few seconds. On a laptop. With #VirtualThreads in #Java25, that’s reality. Mihaela Gheorghe-Roman explains what changed since #JDK21 & why thread-per-request is back. Still running huge thread pools?
Rethink: https://javapro.io/2026/03/05/java-25-and-the-new-age-of-performance-virtual-threads-and-beyond/
-
100k blocking tasks. A few seconds. On a laptop. With #VirtualThreads in #Java25, that’s reality. Mihaela Gheorghe-Roman explains what changed since #JDK21 & why thread-per-request is back. Still running huge thread pools?
Rethink: https://javapro.io/2026/03/05/java-25-and-the-new-age-of-performance-virtual-threads-and-beyond/
-
100k blocking tasks. A few seconds. On a laptop. With #VirtualThreads in #Java25, that’s reality. Mihaela Gheorghe-Roman explains what changed since #JDK21 & why thread-per-request is back. Still running huge thread pools?
Rethink: https://javapro.io/2026/03/05/java-25-and-the-new-age-of-performance-virtual-threads-and-beyond/
-
🚀 Call for Contributors – #JVM #Performance #Benchmarks
If you're interested in contributing to the #JVM #Performance #Benchmarks project - an initiative that gained significant traction in the #Java community through our recent #JDK17 and #JDK21 analyses - check out the repo:
🔗 https://github.com/ionutbalosin/jvm-performance-benchmarks
🧵 DM me or open a PR to get started
-
🚀 Call for Contributors – #JVM #Performance #Benchmarks
If you're interested in contributing to the #JVM #Performance #Benchmarks project - an initiative that gained significant traction in the #Java community through our recent #JDK17 and #JDK21 analyses - check out the repo:
🔗 https://github.com/ionutbalosin/jvm-performance-benchmarks
🧵 DM me or open a PR to get started
-
🚀 Call for Contributors – #JVM #Performance #Benchmarks
If you're interested in contributing to the #JVM #Performance #Benchmarks project - an initiative that gained significant traction in the #Java community through our recent #JDK17 and #JDK21 analyses - check out the repo:
🔗 https://github.com/ionutbalosin/jvm-performance-benchmarks
🧵 DM me or open a PR to get started
-
🚀 Call for Contributors – #JVM #Performance #Benchmarks
If you're interested in contributing to the #JVM #Performance #Benchmarks project - an initiative that gained significant traction in the #Java community through our recent #JDK17 and #JDK21 analyses - check out the repo:
🔗 https://github.com/ionutbalosin/jvm-performance-benchmarks
🧵 DM me or open a PR to get started
-
🚀 Call for Contributors – #JVM #Performance #Benchmarks
If you're interested in contributing to the #JVM #Performance #Benchmarks project - an initiative that gained significant traction in the #Java community through our recent #JDK17 and #JDK21 analyses - check out the repo:
🔗 https://github.com/ionutbalosin/jvm-performance-benchmarks
🧵 DM me or open a PR to get started
-
@svenruppert In #JabRef, we stick with #JDK21, because the new features of JDK22 do not outweigh the updates the effort of Linux distributions packaging our app with a more recent #JDK. Regarding #JavaFX, we always go with the latest release - and also build with the latest EA version to enable testing by Linux users whether their bugs (mostly with Gnome and i3) are fixed. Our #GitHub #workflow is https://github.com/JabRef/jabref/blob/main/.github/workflows/deployment-jdk-ea.yml.
-
@svenruppert In #JabRef, we stick with #JDK21, because the new features of JDK22 do not outweigh the updates the effort of Linux distributions packaging our app with a more recent #JDK. Regarding #JavaFX, we always go with the latest release - and also build with the latest EA version to enable testing by Linux users whether their bugs (mostly with Gnome and i3) are fixed. Our #GitHub #workflow is https://github.com/JabRef/jabref/blob/main/.github/workflows/deployment-jdk-ea.yml.
-
@svenruppert In #JabRef, we stick with #JDK21, because the new features of JDK22 do not outweigh the updates the effort of Linux distributions packaging our app with a more recent #JDK. Regarding #JavaFX, we always go with the latest release - and also build with the latest EA version to enable testing by Linux users whether their bugs (mostly with Gnome and i3) are fixed. Our #GitHub #workflow is https://github.com/JabRef/jabref/blob/main/.github/workflows/deployment-jdk-ea.yml.
-
Dive into the latest advancements in #Java with our latest article on JDK 21's virtual threads: https://bit.ly/4cEppIA
This analysis compares the performance of virtual threads with Open Liberty's thread pool, focusing on key findings such as throughput, ramp-up times, and memory footprint. While virtual threads offer several advantages, they also show unexpected performance issues, especially in CPU-intensive workloads.
This analysis guides Java developers on when and how to use virtual threads in their applications.
-
Dive into the latest advancements in #Java with our latest article on JDK 21's virtual threads: https://bit.ly/4cEppIA
This analysis compares the performance of virtual threads with Open Liberty's thread pool, focusing on key findings such as throughput, ramp-up times, and memory footprint. While virtual threads offer several advantages, they also show unexpected performance issues, especially in CPU-intensive workloads.
This analysis guides Java developers on when and how to use virtual threads in their applications.
-
Dive into the latest advancements in #Java with our latest article on JDK 21's virtual threads: https://bit.ly/4cEppIA
This analysis compares the performance of virtual threads with Open Liberty's thread pool, focusing on key findings such as throughput, ramp-up times, and memory footprint. While virtual threads offer several advantages, they also show unexpected performance issues, especially in CPU-intensive workloads.
This analysis guides Java developers on when and how to use virtual threads in their applications.
-
Dive into the latest advancements in #Java with our latest article on JDK 21's virtual threads: https://bit.ly/4cEppIA
This analysis compares the performance of virtual threads with Open Liberty's thread pool, focusing on key findings such as throughput, ramp-up times, and memory footprint. While virtual threads offer several advantages, they also show unexpected performance issues, especially in CPU-intensive workloads.
This analysis guides Java developers on when and how to use virtual threads in their applications.
-
Dive into the latest advancements in #Java with our latest article on JDK 21's virtual threads: https://bit.ly/4cEppIA
This analysis compares the performance of virtual threads with Open Liberty's thread pool, focusing on key findings such as throughput, ramp-up times, and memory footprint. While virtual threads offer several advantages, they also show unexpected performance issues, especially in CPU-intensive workloads.
This analysis guides Java developers on when and how to use virtual threads in their applications.
-
My article about synchronized on #foojay has reached 5,000 views: https://foojay.io/today/lets-replace-the-synchronized-keyword/ 👏
:java: :foojay: #java #synchronized #virtualthreads #jdk21
-
My article about synchronized on #foojay has reached 5,000 views: https://foojay.io/today/lets-replace-the-synchronized-keyword/ 👏
:java: :foojay: #java #synchronized #virtualthreads #jdk21
-
Comme souvent, quand je bloque sur un sujet, ça devient une page sur mon wiki: https://www.jtips.info/Java/VirtualThread
#jdk #jdk21 #VirtualThreads -
Comme souvent, quand je bloque sur un sujet, ça devient une page sur mon wiki: https://www.jtips.info/Java/VirtualThread
#jdk #jdk21 #VirtualThreads -
Comme souvent, quand je bloque sur un sujet, ça devient une page sur mon wiki: https://www.jtips.info/Java/VirtualThread
#jdk #jdk21 #VirtualThreads -
Comme souvent, quand je bloque sur un sujet, ça devient une page sur mon wiki: https://www.jtips.info/Java/VirtualThread
#jdk #jdk21 #VirtualThreads -
avis partagé !! RT @AlexisHassler Avec le JDK 21, les virtual threads sont séduisants. Par contre au niveau inspection c'est galère. #jdk #jdk21 #VirtualThreads
-
avis partagé !! RT @AlexisHassler Avec le JDK 21, les virtual threads sont séduisants. Par contre au niveau inspection c'est galère. #jdk #jdk21 #VirtualThreads
-
avis partagé !! RT @AlexisHassler Avec le JDK 21, les virtual threads sont séduisants. Par contre au niveau inspection c'est galère. #jdk #jdk21 #VirtualThreads
-
avis partagé !! RT @AlexisHassler Avec le JDK 21, les virtual threads sont séduisants. Par contre au niveau inspection c'est galère. #jdk #jdk21 #VirtualThreads
-
Il n'apparaissent pas avec jstack, jconsole ou visualvm.
Avec jcmd, on les voit avec la commande Thread.dump_to_file, mais pas avec Thread.print 🤯.
#jdk #jdk21 #VirtualThreads -
Il n'apparaissent pas avec jstack, jconsole ou visualvm.
Avec jcmd, on les voit avec la commande Thread.dump_to_file, mais pas avec Thread.print 🤯.
#jdk #jdk21 #VirtualThreads -
Il n'apparaissent pas avec jstack, jconsole ou visualvm.
Avec jcmd, on les voit avec la commande Thread.dump_to_file, mais pas avec Thread.print 🤯.
#jdk #jdk21 #VirtualThreads -
Il n'apparaissent pas avec jstack, jconsole ou visualvm.
Avec jcmd, on les voit avec la commande Thread.dump_to_file, mais pas avec Thread.print 🤯.
#jdk #jdk21 #VirtualThreads -
Avec le JDK 21, les virtual threads sont séduisants. Par contre au niveau inspection c'est galère.
#jdk #jdk21 #VirtualThreads -
Avec le JDK 21, les virtual threads sont séduisants. Par contre au niveau inspection c'est galère.
#jdk #jdk21 #VirtualThreads -
Avec le JDK 21, les virtual threads sont séduisants. Par contre au niveau inspection c'est galère.
#jdk #jdk21 #VirtualThreads -
Avec le JDK 21, les virtual threads sont séduisants. Par contre au niveau inspection c'est galère.
#jdk #jdk21 #VirtualThreads -
"JAVA IS HERE TO STAY!"
#Java developers,
Truly one of the most positive and upbeat Java articles I've encountered in a while. Have a read! Please AMPLIFY!
💜☕️ -
"JAVA IS HERE TO STAY!"
#Java developers,
Truly one of the most positive and upbeat Java articles I've encountered in a while. Have a read! Please AMPLIFY!
💜☕️ -
"JAVA IS HERE TO STAY!"
#Java developers,
Truly one of the most positive and upbeat Java articles I've encountered in a while. Have a read! Please AMPLIFY!
💜☕️ -
"JAVA IS HERE TO STAY!"
#Java developers,
Truly one of the most positive and upbeat Java articles I've encountered in a while. Have a read! Please AMPLIFY!
💜☕️ -
"JAVA IS HERE TO STAY!"
#Java developers,
Truly one of the most positive and upbeat Java articles I've encountered in a while. Have a read! Please AMPLIFY!
💜☕️ -
12 Lessons Learned From Doing The One Billion Row Challenge:
https://foojay.io/today/12-lessons-learned-from-doing-the-one-billion-row-challenge/ -
12 Lessons Learned From Doing The One Billion Row Challenge:
https://foojay.io/today/12-lessons-learned-from-doing-the-one-billion-row-challenge/ -
There has been some interesting discussion on #JakartaEE 11 and #Java servers over on Twitter. The draft of the spec has been updated to require JDK 17 rather than requiring JDK 21. I agree with the decision. To maximize adoption, JakartaEE must support JDK 17 and optionally JDK 21. Dropping JDK 11 is the best we can hope for right now.
#JakartaEE11 #OpenJDK #OpenSource #JDK21 #JDK17 #JDK11 #WildFly #GlassFish #OpenLiberty #Tomcat #Jetty -
There has been some interesting discussion on #JakartaEE 11 and #Java servers over on Twitter. The draft of the spec has been updated to require JDK 17 rather than requiring JDK 21. I agree with the decision. To maximize adoption, JakartaEE must support JDK 17 and optionally JDK 21. Dropping JDK 11 is the best we can hope for right now.
#JakartaEE11 #OpenJDK #OpenSource #JDK21 #JDK17 #JDK11 #WildFly #GlassFish #OpenLiberty #Tomcat #Jetty -
There has been some interesting discussion on #JakartaEE 11 and #Java servers over on Twitter. The draft of the spec has been updated to require JDK 17 rather than requiring JDK 21. I agree with the decision. To maximize adoption, JakartaEE must support JDK 17 and optionally JDK 21. Dropping JDK 11 is the best we can hope for right now.
#JakartaEE11 #OpenJDK #OpenSource #JDK21 #JDK17 #JDK11 #WildFly #GlassFish #OpenLiberty #Tomcat #Jetty -
There has been some interesting discussion on #JakartaEE 11 and #Java servers over on Twitter. The draft of the spec has been updated to require JDK 17 rather than requiring JDK 21. I agree with the decision. To maximize adoption, JakartaEE must support JDK 17 and optionally JDK 21. Dropping JDK 11 is the best we can hope for right now.
#JakartaEE11 #OpenJDK #OpenSource #JDK21 #JDK17 #JDK11 #WildFly #GlassFish #OpenLiberty #Tomcat #Jetty
