Acknowledged replication of Queue across the network

Benchmarks have a natural lifespan that can be improved with more modern hardware. This benchmark was performed 18 March 2020.  Please don’t hesitate to contact us if you have questions about how Chronicle Queue Enterprise will perform today.

A major feature of Chronicle Queue Enterprise is support for TCP and UDP replication across multiple servers to ensure high availability of client infrastructure, whilst there may be inherent latencies within the network, we want to ensure that Queue replication adds minimal overheads. Below is a chart which shows how long it takes to write a 40 byte message then write replicate over TCP have a second acknowledged receipt and finally have the thread read the acknowledged message. The results show that typical latencies varied between 14 and 40 microseconds and the 99th percentile varied between 17 and 56 microseconds dependent on throughput being tested


Want access to exclusive Chronicle content?

Hit the button below and join the Chronicle Community on LinkedIn, for free! You'll get exclusive access to blogs, guides, and video content. Join today!

Want more from Chronicle? Subscribe today!

Something went wrong. Please check your entries and try again.