--- title: "Quarkus Newsletter #71 - August" url: https://daily.dev/posts/quarkus-newsletter-71---august-kkqt5ieis source_url: https://quarkus.io/blog/quarkus-newsletter-71 type: article source: "Quarkus" published: 2026-08-13T23:11:35.786Z updated: 2026-08-13T23:13:32.156Z tags: ["java", "quarkus", "jvm"] reading_time: 2 upvotes: 1 comments: 0 language: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Quarkus Newsletter #71 - August **[Quarkus](https://daily.dev/sources/quarkus)** · 2 min read · 1 upvotes · 0 comments ## Summary A roundup covering several Quarkus community posts: a benchmarking correction where fixing measurement bias raised Spring's numbers while Quarkus's stayed flat, an investigation into virtual thread pooling advice from OpenJDK, a Project Leyden-based approach to faster JVM startup in containers, a guide to building hardened Quarkus images with Jib and Java 25, and a small extension that prints an application name banner at startup. Also mentions Quarkus Insights episodes and upcoming events. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### Should I pool virtual threads in Java to improve performance? OpenJDK's own guidance is not to pool virtual threads, and testing that advice with real data confirmed why: pooling broke performance, and attempts to fix the JVM to compensate made things worse rather than better. Virtual threads are designed to be cheap and disposable, so creating new ones instead of reusing pooled threads aligns with how the JVM schedules them. _Developers tuning JVM concurrency can track virtual thread guidance and gotchas like this on daily.dev._ ### How can I get faster JVM startup times in a containerized Quarkus application without losing diagnostics? Project Leyden combined with Quarkus offers a deployment option that speeds up container startup while still preserving JVM diagnostics, agent support, and compatibility with existing tooling, giving teams a middle ground between raw JVM startup and more aggressive native-image approaches. _Teams weighing JVM startup tradeoffs can follow Quarkus and Project Leyden updates through daily.dev._ ## Similar posts on daily.dev - [Quarkus Newsletter \#66 - March](https://daily.dev/posts/quarkus-newsletter-66---march-bm24fbp4x) · Quarkus · 0 upvotes · 0 comments - [Quarkus Newsletter \#65 - February](https://daily.dev/posts/quarkus-newsletter-65---february-7fnk26ytp) · Quarkus · 0 upvotes · 0 comments - [Quarkus Newsletter \#64 - January](https://daily.dev/posts/quarkus-newsletter-64---january-va4c2shit) · Quarkus · 2 upvotes · 0 comments --- Tags: [#java](https://daily.dev/tags/java), [#quarkus](https://daily.dev/tags/quarkus), [#jvm](https://daily.dev/tags/jvm) [View this post on daily.dev](https://daily.dev/posts/quarkus-newsletter-71---august-kkqt5ieis)