Optimising your memory allocations in Java could make far more difference than your choice of Garbage Collector, and may even change which garbage collector is best. Chronicle FIX already persists each message; what if we use SLF4J to write another copy?
blog.vanillajava.blog/2026/06/why-yo…
CEO of @Chronicle_SW (Software)
Java Champion, author of Vanilla Java, performance specialist, 13K answers on StackOverflow
- AI can be used as a trial developer of your software. If an AI can write effective code, test, and tune it, that a great start. In this exercise, I get an AI to write a low latency benchmark in Java for Chronicle FIX (closed source so not indexed) blog.vanillajava.blog/2026/06/testin…
- I am all in on AI writing 20K LOC a day. I use it for mock systems, quick prototypes, and sample use cases. It works well enough, but it's not worth reading, usually not worth adding as test cases, and certainly not worth using in production.
- The problem isn't technical; inefficient use of AI is expensive. My team uses Claude and Codex nearly every day, and I have generated ~1M LOC this year. Yet AI accounts for ~1% of our costs, and I don't think spending much more would help.
- The biggest benefit of AI is that it serves as a rapid-learning tool to broaden your knowledge. It can help close gaps in your knowledge up to average levels with relatively little effort

