GC log analysis and collector tuning across G1, ZGC, Shenandoah, Parallel, and Azul C4. Reducing pause times, allocation pressure, and the latency tax that garbage collection puts on your workload.
Analyzing Java heaps in the hundreds of gigabytes and into the terabyte range — using tooling specifically built to scale beyond standard approaches.
Forget tips and tricks with a version shelf life. Learn jPDM: a structured, repeatable approach to performance diagnostics. Find regressions faster, surface root causes you didn't know about with confidence — regardless of which version of Java you're on.
Finding and fixing performance bottlenecks in Java applications — code, architecture, JVM configuration, allocation patterns, or elsewhere in the system. Can result in reduced EC2 costs and improved p99 latencies.
A benchmark is only useful if it measures what you think it's measuring. Coordinated omission, harness effects, timing artifacts, environmental noise — there are many ways for that to go wrong. I design and review benchmarks less prone to those failures.
What follows is my solution so don't read any further. Spoiler alert, solution about to start.