Analysis updated 2026-08-07 · repo last pushed 2026-08-03
Test your RabbitMQ setup before a big product launch to confirm it can handle expected traffic surges.
Compare performance before and after upgrading to a larger server or adding cluster nodes.
Generate an HTML report of benchmark results to share with your team or track performance over time.
Stress-test a staging environment to find the throughput and latency limits of your messaging infrastructure.
| rabbitmq/rabbitmq-perf-test | getactivity/devicecompat | peng-zhihui/bluetoothtouch | |
|---|---|---|---|
| Stars | 418 | 513 | 533 |
| Language | Java | Java | Java |
| Last pushed | 2026-08-03 | 2026-02-11 | 2021-07-09 |
| Maintenance | Active | Maintained | Dormant |
| Setup difficulty | easy | easy | moderate |
| Complexity | 2/5 | 2/5 | 2/5 |
| Audience | ops devops | developer | general |
Figures from each repo's GitHub metadata at analysis time.
Requires a running RabbitMQ server to test against and at least Java 8 installed on your machine.
RabbitMQ PerfTest is a tool for stress-testing RabbitMQ message servers. If your application relies on RabbitMQ to move messages between services, this tool helps you find out how much traffic your setup can handle before things slow down or break. You run it against your RabbitMQ server, and it simulates producers sending messages and consumers receiving them, then reports back on throughput, latency, and other performance metrics. At its core, the tool talks to a RabbitMQ cluster using the AMQP messaging protocol. You launch it from the command line and tell it how many message producers and consumers to simulate. By default it runs one of each, but you can configure many more parameters through command-line options. There is also a companion feature that wraps these benchmark runs and generates an HTML page with the results, which is handy for sharing findings with a team or keeping a record of how performance changes over time. This is primarily useful for engineers or teams operating RabbitMQ in production or staging environments. For example, if you are planning a big product launch and expect a surge in traffic, you could use this tool to verify your messaging infrastructure will cope. It is also practical when evaluating infrastructure changes, say you are upgrading to a larger server or adding more nodes to your cluster, and want concrete numbers showing whether the change actually improved throughput or reduced latency. The tool is distributed as a standalone Java application, a Docker image, or a library you can pull into a Java project. It requires at least Java 8, though newer versions are recommended. It is maintained by the official RabbitMQ team at Broadcom, so it tracks closely with RabbitMQ's own development. The project is open source under a triple license (MPL, GPL, and Apache), giving users flexibility in how they adopt it.
A tool for stress-testing RabbitMQ message servers by simulating producers and consumers, then reporting throughput, latency, and other performance metrics. Run it from the command line to find out how much traffic your setup can handle before things slow down or break.
Mainly Java. The stack also includes Java, AMQP, Docker.
Active — commit in last 30 days (last push 2026-08-03).
Triple-licensed under MPL, GPL, and Apache, so you can choose whichever license fits your needs when using or distributing the tool.
Setup difficulty is rated easy, with roughly 5min to a first successful run.
Mainly ops devops.
This repo across BitVibe Labs
Verify against the repo before relying on details.