<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>David Vlijmincx on JAVAPRO International</title><link>https://javapro-en.svenruppert.com/authors/david-vlijmincx/</link><description>Recent content in David Vlijmincx on JAVAPRO International</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Thu, 16 Oct 2025 07:00:03 +0000</lastBuildDate><atom:link href="https://javapro-en.svenruppert.com/authors/david-vlijmincx/index.xml" rel="self" type="application/rss+xml"/><item><title>Async IO with Java and Panama: Unlocking the Power of IO_uring</title><link>https://javapro-en.svenruppert.com/async-io-with-java-and-panama-unlocking-the-power-of-io_uring/</link><pubDate>Thu, 16 Oct 2025 07:00:03 +0000</pubDate><guid>https://javapro-en.svenruppert.com/async-io-with-java-and-panama-unlocking-the-power-of-io_uring/</guid><description>&lt;p&gt;When I first started exploring Virtual Threads in Java, I wanted to understand everything about them—their yielding behavior,&lt;br&gt;
performance characteristics, and limitations. This journey led me to an interesting challenge: file I/O operations cause&lt;br&gt;
Virtual Threads to become &amp;ldquo;pinned&amp;rdquo; to platform threads, limiting their effectiveness for I/O-heavy applications.&lt;/p&gt;
&lt;p&gt;This pinning issue has been widely acknowledged across the Java community. It&amp;rsquo;s mentioned in the &lt;a href="https://openjdk.org/jeps/425"&gt;Virtual Threads JEP&lt;/a&gt;,&lt;br&gt;
discussed on &lt;a href="https://www.reddit.com/r/java/comments/1h0cr5g/comment/lz3lv11/"&gt;Reddit threads&lt;/a&gt;, debated on &lt;a href="https://mail.openjdk.org/pipermail/loom-dev/2024-June/006638.html"&gt;mailing lists&lt;/a&gt;,&lt;br&gt;
and highlighted in the &amp;ldquo;&lt;a href="https://cr.openjdk.org/~rpressler/loom/loom/sol1_part1.html"&gt;State of Loom&lt;/a&gt;&amp;rdquo;. The consistent message: File I/O and Virtual Threads don&amp;rsquo;t play nicely together.&lt;/p&gt;</description></item></channel></rss>