AI-Generated Java Benchmarks for Chronicle-FIX

Chronicle Software CEO Peter Lawrey had AI build a JLBH benchmark for Chronicle-FIX, then corrected its assumptions along the way; from percentile choices to over-engineered code. Round-trip latency landed at 2.4–3.7 microseconds. The real value wasn't the code produced, but what the exercise revealed about the system and the AI itself.

Running Chronicle on Java 17 and Later: The Required JVM Arguments, Explained

Why Low-Latency Java Still Needs Off-Heap Memory Management

Why low-latency Java still requires discipline?

Where AI Helps, Where It Hurts — and How To Gate the Risk in Low-Latency Systems

Market Making and Liquidity Provision in the Age of Algorithmic Trading

To function efficiently and facilitate trading, many niches depend on market making, the practice of quoting two-sided prices. By providing liquidity, market makers ensure smooth and efficient price discovery.

Mastering Market Complexity With Chronicle

Optimise Trading Systems for the Cloud with Microservices

Chronicle Software Wins “Best FIX Engine Provider” at TradingTech Insight Awards 2025

Regulatory Compliance in Algorithmic Trading

How Brokers Can Improve Performance and Reporting To Win Over Institutional Clients

Demystifying Low-Latency Algorithmic Trading