<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Threads on JAVAPRO International</title><link>https://javapro-en.svenruppert.com/tags/threads/</link><description>Recent content in Threads on JAVAPRO International</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Thu, 05 Mar 2026 07:00:01 +0000</lastBuildDate><atom:link href="https://javapro-en.svenruppert.com/tags/threads/index.xml" rel="self" type="application/rss+xml"/><item><title>Java 25 and the New Age of Performance: Virtual Threads and Beyond</title><link>https://javapro-en.svenruppert.com/java-25-and-the-new-age-of-performance-virtual-threads-and-beyond/</link><pubDate>Thu, 05 Mar 2026 07:00:01 +0000</pubDate><guid>https://javapro-en.svenruppert.com/java-25-and-the-new-age-of-performance-virtual-threads-and-beyond/</guid><description>&lt;h2 id="summary"&gt;Summary&lt;/h2&gt;
&lt;p&gt;Project Loom continues to reshape how we handle concurrency in the JVM, and Java 25 makes virtual threads more accessible to developers than ever. In this article, we’ll take a closer look at how virtual threads work, how they differ from platform threads, and where they provide the most benefit in real-world applications. We’ll also include performance benchmarks and a step-by-step guide for refactoring blocking I/O services to use virtual threads.&lt;/p&gt;</description></item><item><title>Java 24: A Story of Code, Conflict, and Conquer</title><link>https://javapro-en.svenruppert.com/java-24-a-story-of-code-conflict-and-conquer/</link><pubDate>Wed, 27 Aug 2025 07:00:03 +0000</pubDate><guid>https://javapro-en.svenruppert.com/java-24-a-story-of-code-conflict-and-conquer/</guid><description>&lt;p&gt;In a digital world far away from here, runs a Java application without problems. The logs are quiet, the servers are stable, and Emma and her team live in peace. But then, the first attack arrives! First innocent. A little spike in the memory use. But than another, and another. Within a couple of days, it turns into a disaster. Garbage collectors are going wild. The latency rises. The servers are shaking. The memory realm is flooded by invisible enemies: unnecessarily inflated object headers. They hide in every object, wasting valuable bytes and creating chaos in the heap.&lt;/p&gt;</description></item></channel></rss>