How fast is it, really? Let’s find out and keep track.
We benchmark LavinMQ to see how it performs under pressure. This page gives you the latest numbers, previous runs, our full test setup, and some honest thoughts on the limitations. The goal is to be transparent. So you can form your own opinion.
Latest benchmark
This is the latest snapshot of LavinMQ’s performance.
Burstable general-purpose
t4g: Uses ARM based AWS Graviton2 processors and are a cost-effective, burstable general-purpose instance type.
t4g.micro
363,440 msgs/s
361,397 msgs/s
2 vCPU, 1 GiB RAM
Memory optimized
r7g: Uses ARM based AWS Graviton3 process are optimized for memory intensive workloads.
r7g.medium
570,294 msgs/s
570,088 msgs/s
1 vCPU, 8 GiB RAM
CPU optimized
c8g: Uses ARM based AWS Graviton4 and are ideal for compute-intensive workloads, such as high performance computing.
c8g.large
788,907 msgs/s
788,540 msgs/s
2 vCPU, 4 GiB RAM
Storage optimized
i7i, i7ie: Uses AMD based 5th generation Intel Xeon Scalable and are optimized for storage-intensive workloads that require high-speed access to data residing on local NVMe storage.
i7i.large
917,403 msgs/s
917,173 msgs/s
2 vCPU, 16 GiB RAM
Transparent setup. Reproducible code.
How we run the tests
We use open-source tools and custom scripts to run our benchmarks. Nothing hidden or proprietary. The full setup is on GitHub, including:
- Test scenarios
- Infrastructure configuration
- Data collection and visualization
Want to run the same test?
Clone the repo and follow the instructionsSome honest criticism of our approach
What These Numbers Don’t Show
No benchmark is perfect. Here are some caveats to keep in mind:
- Synthetic tests don’t reflect every real-world workload
- Network and disk performance can skew results
- Benchmarks are snapshots, not full stories
Want to run the same test?
Clone the repo and follow the instructionsGot a benchmark of your own?
We’d love to see it.
If you’ve done your own testing of LavinMQ (or compared it to other brokers), let us know. We may link to third-party benchmarks here in the future.
Contact us