Table of Contents
--
-
- Throughput to an Unsubscribed Topic -
- Queue Load/Unload -
- Partitioned Load Scenarios -
- Fan In/Out Load Scenarios -
Overview
-- This report was generated using the JMS-benchmark tool. It - provides a comparative benchmark of messaging servers that implement the JMS 1.1 - specification. It covers a wide variety of common usage scenarios. Each scenario is warmed up for 3 seconds before - the performance samples are taken. -
- --
-
- Mac Pro Model: MacPro3,1 -
- CPU: 2 x 3 GHz Quad-Core Intel Xeon -
- Memory: 8 GB 800 MHz DDR2 -
- OS: Mac OS X 10.6.6 -
- Disk: SATA 7200 RPM -
- Java: 64-Bit 1.6.0_22 -
Throughput to an Unsubscribed Topic
-- A single producer sending non-persistent messages to a topic that does not have an consumers attached. -
-
- With a 20 b Playload- - |
- With a 1 k Playload- - |
- With a 256 k Playload- - |
-
Queue Load/Unload
-
- Non Persistent Load-- A producer sending non-persistent messages with 20 byte payloads to a queue without any attached consumers. - - - |
- Persistent Load-- A producer sending persistent messages with 20 byte payloads to a queue without any attached consumers. Each - send requests a receipt to achieve guaranteed delivery. - - - |
- Unload-- A consumer receiving the messages previously sent to the queue but without any attached producers. - - - |
-
Partitioned Load Scenarios
-- These scenarios sample performance as partitioned load is applied. - Each destination only has 1 and only 1 producer and consumer attached. -
- The graphs below display the results of all the following scenario combinations: -
-
-
- Queue: The point to point messaging domain -
- Topic: The publish subscribe messaging domain -
- Persistent: Messages are sent persistent and with a receipt request to achieve guaranteed delivery. -
- Non Persistent: Messages are sent non-persistent and without a receipt request -
- 20 b Message: Messages payloads are 20 bytes in size -
- 1 k Message: Messages payloads are 1 kilobytes in size -
- 256 k Message: Messages payloads are 256 kilobytes in size -
- 1x1x1: 1 producer, 1 destination, 1 consumer -
- 5x5x5: 5 producers, 5 destinations, 5 consumers -
- 10x10x10: 10 producers, 10 destinations, 10 consumers -
Non Persistent | Persistent | |||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Queue |
-
|
-
| ||||||||||||||||||||||||||||||||
Topic |
-
|
-
|
Fan In/Out Load Scenarios
-- These scenarios multiple consumers and producers communicate via one shared destination. All messages sent have - a 20 byte payload. -
- The graphs below display the results of all the following scenario combinations: -
-
-
- Queue: The point to point messaging domain -
- Topic: The publish subscribe messaging domain -
- Persistent: Messages are sent persistent and with a receipt request to achieve guaranteed delivery. -
- Non Persistent: Messages are sent non-persistent and without a receipt request -
Non Persistent | Persistent | |||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Queue |
-
|
-
| ||||||||||||||||||||||||||||||||
Topic |
-
|
-
|