JFR vs async-profiler for production CPU profiling
For production CPU profiling on a JDK 21 or 25 box in 2026, default to async-profiler with --jfrsync : roughly 1% overhead at -i 10ms , no safepoint bias.
Java News | Enterprise Java & Spring
Java News covers enterprise Java development, Spring Boot, and JVM performance.
For production CPU profiling on a JDK 21 or 25 box in 2026, default to async-profiler with --jfrsync : roughly 1% overhead at -i 10ms , no safepoint bias.
If your CI bill is dominated by Docker pulls and your @DataJpaTest classes each create their own database, the choice between Testcontainers and zonky's.
As of: March 22, 2026 — Azul Zulu Prime 24.03 Quick nav Why does the SIGILL only fire after a CRaC restore? What does the crash look like in a…
I still remember the day my team hit a wall with our CI pipeline. We were maintaining a massive Spring Boot monolith—over 80 modules, half a million lines.
I spent last weekend staring at Datadog dashboards, watching our Java microservices take their sweet, agonizing 14 seconds to spin up during a sudden.
Actually, I should clarify - another Friday night ruined. Well, that's not entirely accurate. I spent three hours last weekend trying to figure out why a.
Well, I have to admit, I've had a love-hate relationship with Gradle. Mostly hate, if I'm being honest. But last Tuesday, I decided to bump our main.
Well, that's not entirely accurate - for years, despite being a "Java guy," I actually wrote all my utility scripts in Python or Bash .
Actually, I spent my Friday night patching three different legacy clusters because apparently, we haven't learned our lesson about HTTP verbs yet.
Well, I've been running them in production on our payment processing service for the last six months. And honestly? It's mostly great. Mostly.