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.

v2.3.0

Latest benchmark

This is the latest snapshot of LavinMQ’s performance.

Instance type

t4g.micro

Avg. Publish rate

363,440 msgs/s

Avg. Consume rate

361,397 msgs/s

Comment

2 vCPU, 1 GiB RAM

Instance type

r7g.medium

Avg. Publish rate

570,294 msgs/s

Avg. Consume rate

570,088 msgs/s

Comment

1 vCPU, 8 GiB RAM

Instance type

c8g.large

Avg. Publish rate

788,907 msgs/s

Avg. Consume rate

788,540 msgs/s

Comment

2 vCPU, 4 GiB RAM

Instance type

i7i.large

Avg. Publish rate

917,403 msgs/s

Avg. Consume rate

917,173 msgs/s

Comment

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

Some 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

Got 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.

Clone the repo and follow the instructions