Viewing profile — peter_lawrey

TL;DR: Markdown for AI working documents, AsciiDoc for curated human-reviewed specs, HTML only as a publishing target.

AI has improved over the last 6 months, with quality in the mid-range. It takes less effort to get it to produce a mediocre-to-average-quality solution. In many cases, this is good…

A common mistake appears to be that only when women have fewer than 1 child does the population drop long term...

This post explores using AI as a mock User, something AI is particularly suited for. - AI remembers nothing from previous tests by default. - It has a broad knowledge set - It read…

In this post I look at a simple event to response latency benchmark, MarketDataSnapshot to NewOrderSingle at 50K/s for 30 minutes using JLBH to test Chronicle-FIX. The goal is to c…

Thank you for the feedback

Good feedback

This is a high-level article; for lower-level details, I also posted. https://blog.vanillajava.blog/2026/06/testing-java-memory-ma... https://blog.vanillajava.blog/2026/06/why-you-…

7 Frequently Asked Questions about Low-latency Microservices in 7 minutes

Most Iterators should be placed on the stack anyway. If they are not and you have a random access collection like ArrayList you can use an index, but this is rarely needed. If you …

A friend of mine is working at Oracle on collections that support primitives e.g. List , Set https://openjdk.org/jeps/8261529

Iterators tend to be placed on the stack in hot code. In the benchmark I had to make sure these object weren't optimised away.

Mutable objects have their own issues, which can catch people out by surprise. Having good test coverage is important.

Reusing your objects can be confusing for other developers. You need to be careful with anything exposed via an API, however internally you can me more optimised.

In each case the default settings were used (i.e. no options were provided). In both Java 8 (Parallel GC) and Java 11+ (G1), As the GC was a small portion of the time, changing the…

The GC isn't involved with allocation, the expensive bit here. The GC handles the clean up. The allocations create memory pressure that can easily saturate the bus to DDR if you ar…

Right, it's the total object count at runtime that matters, not how many lines of code could create an object.

This is where using a profiler like YourKit or Flight Recorder is your friend. It will show you the objects that can't be optimised away and where code bottlenecks are. It's hard t…

or FPGA