Little project to benchmark JMS providers
JavaScript CSS Scala Shell
Latest commit 705666b May 7, 2014 @chirino Merge pull request #8 from christian-posta/master
updated stompjms-client version to 1.19
Failed to load latest commit information.
bin Upgrade hornetq version. May 17, 2013
jms-benchmark-hornetq Upgrade hornetq version. May 17, 2013
jms-benchmark-qpid-1.0 Fixing compiler warnings. Feb 21, 2013
jms-benchmark-qpid Support hooking into the load start point. Apr 15, 2013
jms-benchmark-stomp updated stompjms-client version to 1.19 May 6, 2014
jms-benchmark better client shutdown. May 30, 2013
project Revert to scala 2.8.1 Jul 12, 2011
reports Use updated perf numbers. May 28, 2013
src/main/html Fix title. Jan 31, 2012
.gitignore Added run scripts to automate benchmarking against the latest release… Dec 25, 2011
license.txt adding some notices Oct 29, 2010 Changing the AMQP references to JMS May 17, 2011
pom.xml Update the benchmark output file after each scenario run and if the b… May 10, 2013 Update the script in the readme. GitHub does not seem to support tarb… Dec 6, 2012

JMS Benchmark

A benchmarking tool for JMS 1.1 servers. The benchmark covers a wide variety of common usage scenarios.

Servers Currently Benchmarked

  • Apache ActiveMQ (Openwire protocol)
  • Apache ActiveMQ Apollo (STOMP and Openwire protocols)
  • HornetQ (Core protocol)

Just looking for the Results?

The numbers look different depending on the Hardware and OS they are run on:

Running the Benchmark

Just run:


or one of the server specific benchmark scripts like:


Tested to work on:

  • Ubuntu 11.10
  • Amazon Linux
  • OS X

The benchmark report will be stored in the reports/$(hostname) directory.

Running the Benchmark on an EC2 Amazon Linux 64 bit AMI

If you want to run the benchmark on EC2, we recommend using at least the c1.xlarge instance type. Once you have the instance started just execute the following commands on the instance:

sudo yum install -y screen
curl >
jar -xvf 
chmod a+x ./jms-benchmark-master/bin/*
screen ./jms-benchmark-master/bin/benchmark-all

The results will be stored in the ~/reports directory.