Optimizing nanosecond operations: when the CPU cache matters
A check took 29 s. Removing it saved 24 s - the rest moved to a line we didn't touch. Why?
7 articles in this category · 51,191 views.
RSS feed
A check took 29 s. Removing it saved 24 s - the rest moved to a line we didn't touch. Why?

Suneet Kamath
2,620 viewsIn the era of vibe coding—where large amounts of code are introduced or refactored in short bursts, often with the help of LLMs—you need …

Angelo Rubini
2,158 viewsProfiling a Java Application Running Inside an Unikernel with JProfiler Unikernels are often associated with minimalism and tight resource …

Daniel Witkowski
4,004 viewsThe Hidden Cost of “Good Enough” Code A few weeks ago, Kirk Pepperdine published a fascinating performance challenge — a small Java code …

Igor Kulakov
5,736 viewsAnalyzing a curious bottleneck in IntelliJ IDEA using the built-in IntelliJ Profiler and several handy debugger features.

Nasim Salmany
20,858 viewsProfiling performance issues and establishing robust monitoring and observability are critical for maintaining the health and efficiency of …

Lee Sheinberg
15,491 viewsIn this article, I will share why my team decided to start a Java profiler, the list of profilers we found that are suited for profiling …