Chronicle Software OG Image (4)

60% faster TCP/IP within Java One of the major drivers at Chronicle Software is the constant push to remove latency from technology stack , this involves constant analysis and work on all aspects that can add latency. One area we have recently been concentrating on is optimizing the Chronicle network latency that underpins Chronicle Queue…

Read More
Chronicle Software OG Image (5)

One of the major benefits with using any Chronicle product is that we aim for almost Zero Garbage Collection (GC) there are several benefits to reducing Garbage:- Pausing for Garbage Collection happens less often. Creating fewer objects, reduces the overhead of allocating and clearing the object in the first place. An indirect benefit comes from…

Read More
Chronicle Software OG Image (5)

By Peter Lawrey, CEO at Chronicle Software. Regulated trading systems need to record the reasons behind every decision they make with minimal impact on performance. Chronicle Software has worked with investment banks and hedge funds to deliver trading services with a record everything model and low microsecond latencies. Today’s more stringent regulatory environment is placing…

Read More
Chronicle Software OG Image (4)

Overview The FIX Trading Community web site has posted a list of common questions about FIX Engines. This page brings together our answers for these questions. For more details on Chronicle FIX Capabilities/throughput Chronicle FIX supports; 100,000 messages per second per core. (NewOrderSingle / ExecutionReport sized messages) FIX Services which need to have a 30 micro-seconds tick…

Read More
Chronicle Software OG Image (2)

Compared to a year ago, we have significantly improved the throughput at which we can achieve the 99%ile (worst one in 100). What tools and tricks did we use to achieve that? What are we testing? Chronicle Queue appends messages to a file while another thread or process can be reading it. This gives you…

Read More
Chronicle Software OG Image (1)

David Schmitz presented an excellent talk on what he sees as best practices in using Event Sourcing. Chronicle Software has two very different event sourcing frameworks Chronicle Microservices Framework (CMF) and Chronicle Decentred. This talk is useful in highlighting how they differ with each other and other Event Sourcing solutions. CMF is built on Chronicle Queue and is designed for low latency…

Read More
Chronicle Software OG Image (3)

Object pools were popular before Java 5.0, however, more efficient allocation made most of these pools a needless complication. Can an Object Pool still make sense and how fast do they need to be? Overview Up to Java 5.0 using object pools could significantly improve performance. However, from Java 5.0, the cost of using naive…

Read More
Chronicle Software OG Image (2)

In 2006, Java 5.0 was released with StringBuilder, a more lightweight and sane version of StringBuffer. The Javadoc for Java 5.0 for StringBuffer notes As of release JDK 5, this class has been supplemented with an equivalent class designed for use by a single thread, StringBuilder. The StringBuilder class should generally be used in preference…

Read More