Big-O Was Never the Bottleneck. The Cache Line Was.
Two independent variables, two threads, zero shared state, and half the throughput gone. A short tour of why, in low-latency Java, the memory layout beats the algorithm.
Every piece I publish, newest first. They live on Medium, in The Converging Line; the RSS feed (opens in a new tab) brings each one as it comes out.
2 pieces tagged low-latency
Two independent variables, two threads, zero shared state, and half the throughput gone. A short tour of why, in low-latency Java, the memory layout beats the algorithm.
Java has had a native interop story since 1.1. It was always broken. FFM API, finalized in Java 22, finally fixes it without a single line of C glue code.