Vanilla Java: Synchronized vs Lock performance

Vanilla Java: Synchronized vs Lock performance

Mechanical Sympathy: Memory Barriers/Fences

Mechanical Sympathy: Memory Barriers/Fences

Mike's Tech Ramblings: Now Offically an OpenJDK Contributor

Mike's Tech Ramblings: Now Offically an OpenJDK Contributor

Mechanical Sympathy: Processor Affinity - Part 1

Mechanical Sympathy: Processor Affinity - Part 1

Mechanical Sympathy: Let The Caller Choose

Mechanical Sympathy: Let The Caller Choose

Accessing the class object in a static context « Otaku, Cedric's blog

Accessing the class object in a static context « Otaku, Cedric's blog

disruptor - Concurrent programming framework - Google Project Hosting

disruptor - Concurrent programming framework - Google Project Hosting

Bad Code: The Invisible Threat | Javalobby

Bad Code: The Invisible Threat | Javalobby

The LMAX Architecture

LMAX is a new retail financial trading platform. As a result it has to process many trades with low latency. The system is built on the JVM platform and centers on a Business Logic Processor that can handle 6 million orders per second on a single thread. The Business Logic Processor runs entirely in-memory using event sourcing. The Business Logic Processor is surrounded by Disruptors - a concurrency component that implements a network of queues that operate without needing locks. During the design process the team concluded that recent directions in high-performance concurrency models using queues are fundamentally at odds with modern CPU design.