Throughput Benchmarks upto 15 million messages Per Second

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

We performed some benchmarking to test our sustained throughput of 15 million messages per second of various size messages

We did this in various scenarios using various Chronicle products and the results are below

All tests were run on a 2 x 12 core Xeon E5-2650 v4 @ 2.20GHz, with queues backed by tmpfs

Queue: Sustained Throughput, 1 Writer, 1 Reader (Serial)

The sustained throughput for 1 Writer and 1 Reader running serially (all writes completed prior to reading) are shown below for Queue Java and C++.

Higher is better.

Queue: Sustained Throughput, 1 Writer, 1 or 5 Readers (Parallel)

The sustained throughput for 1 Writer and 1 or 5 Reader(s) running in parallel are shown below for Queue Java and C++.

Note, for parallel runs the read throughput is limited to the maximum write throughput so only the read result is shown. The test was run separately with 1 and 5 concurrent readers respectively.

Higher is better.


The benchmarks illustrate that all versions of Chronicle can easily handle above 2 million 250 byte messages per seconds.

As the packet size increases obviously the throughput declines but we are still seeing on average around 1 million 1500 bytes messages per second

For more information on the benchmarks and methodology please contact us on

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.