This section shows results achieved running the different use cases on the z/OS platform.

Before using performance information, be sure to read the general information under Notices.

The results in this section were obtained by running sufficient copies of each message flow so that in most cases the system CPU utilisation was 80% or greater.

Information provided

The results provided in this section include the following performance data:

Message Size:
Records the approximate size of the message that is used as input to the test, not including the message header. This is the size of the XML or equivalent non-XML message payload.
Persistent State:
Indicates whether the messages used in the test is persistent or not.This state can have the following two values:

  • The value Full Persistent is used to indicate that the message tested is persistent.
    • This value is applicable only to WebSphere MQ messages.
    • If a message is persistent, WebSphere MQ ensures that the message is not lost when a failure occurs, by copying it to disk.
  • The value Non Persistent is used for other types of messages.
Message Rate:
Indicates the number of round trips or message flow invocations per second.
% CPU Busy:
Indicates the percentage of CPU usage on the server machine. This includes the total of CPU used by all processes: IBM Integration Bus, WebSphere MQ queue manager, database manager and others. The rate is expressed as a percentage of the CPU capacity that is used by all processors on the server machine.
CPU ms/msg:
Indicates the overall CPU cost per message, that is, the CPU milliseconds per message.

  • You can calculate the value of the CPU cost per message by using the following formula:
    • ((Number of cores * 1000) * (% of CPU / 100)) / Message Rate.
  • This cost includes IBM Integration Bus, WebSphere MQ, DB2, and any operating system costs.
  • Note: The results are specific to the system on from which they have been obtained. If you want to project (or predict) message processing capacity for other systems, you must make a suitable adjustment to allow for differences in the capacity of the two systems.

Performance Results

Typically, as the message size increases, the message rate decreases, and the cost of CPU per message increases.
Persistent MQ messages are written to the MQ log on disk. This causes an overhead in CPU and IO costs and a reduction in message rate. The speed of disk on which the MQ log is configured becomes a key factor. See Tuning for more information.
For details on the measurement environment, see Measurement environment.

When planning a system, it is important to understand the complexities of the processing required so that adequate resources can be provided to meet the requirements of the particular situation.



Aggregation

Non Persistent Full Persistence
Msg Size Msg Rate % CPU Busy CPU ms/msg Msg Rate % CPU Busy CPU ms/msg
256b 2010.6 96.1 1.9 1178.4 93.9 3.2
2kB 1951.4 99.9 2.0 1106.1 96.7 3.5
20kB 1048.1 98.9 3.8 621.6 97.6 6.3
200kB 174.7 100.0 22.9 90.3 53.3 23.6
2000kB 15.3 99.8 260.4 7.7 36.6 189.4
20000kB 0.6 51.0 3513.8 0.3 26.4 3411.6

Coordinated Request/Reply

Non Persistent Full Persistence
Msg Size Msg Rate % CPU Busy CPU ms/msg Msg Rate % CPU Busy CPU ms/msg
256b 2492.3 99.0 1.6 1595.3 95.6 2.4
2kB 1614.5 99.8 2.5 1247.2 98.6 3.2
20kB 397.0 100.0 10.1 338.2 99.3 11.7
200kB 42.7 100.0 93.6 39.9 99.1 99.4
2000kB 3.9 100.0 1015.2 3.9 99.9 1013.7
20000kB 0.4 100.0 10256.4 0.4 100.0 10256.4

Large Messaging

Non Persistent Full Persistence
Msg Size Msg Rate % CPU Busy CPU ms/msg Msg Rate % CPU Busy CPU ms/msg
256b 9505.9 98.5 0.4 2889.9 52.5 0.7
2kB 6790.7 97.6 0.6 2051.7 50.8 1.0
20kB 1166.3 100.0 3.4 228.6 24.8 4.3
200kB 126.5 97.1 30.7 35.1 33.4 38.1
2000kB 12.6 97.3 308.7 3.8 54.1 571.1
20000kB 0.8 64.1 3373.7 0.2 27.8 5302.9

Message Routing

Non Persistent Full Persistence
Msg Size Msg Rate % CPU Busy CPU ms/msg Msg Rate % CPU Busy CPU ms/msg
256b 17733.2 98.8 0.2 4459.1 48.3 0.4
2kB 16082.1 96.9 0.2 3608.9 40.1 0.4
20kB 2624.6 21.1 0.3 1835.0 27.8 0.6
200kB 279.5 7.3 1.1 205.3 11.7 2.3
2000kB 26.1 6.4 9.8 19.1 10.8 22.7
20000kB 2.6 6.2 97.3 0.5 3.5 255.6

Transforming a message

Non Persistent Full Persistence
Msg Size Msg Rate % CPU Busy CPU ms/msg Msg Rate % CPU Busy CPU ms/msg
256b 15421.3 97.8 0.3 4318.4 51.0 0.5
2kB 9540.7 93.6 0.4 3516.1 55.5 0.6
20kB 2075.1 100.0 1.9 1579.9 96.5 2.4
200kB 221.9 100.0 18.0 163.4 91.2 22.3
2000kB 21.5 100.0 186.5 12.3 61.9 201.3
20000kB 1.1 54.8 2086.1 0.5 26.1 2086.4

File out and file in

Non Persistent
Msg Size Msg Rate % CPU Busy CPU ms/msg
256b 3195.6 99.6 1.2
2kB 3079.4 97.2 1.3
20kB 2508.6 95.9 1.5
200kB 267.7 33.3 5.0
2000kB 25.7 30.0 46.6
20000kB 2.5 17.2 271.5

SOAP Consumer

Non Persistent
Msg Size Msg Rate % CPU Busy CPU ms/msg
256b 4867.1 97.7 0.8
2kB 3606.3 93.8 1.0
20kB 1202.1 97.5 3.2
200kB 126.1 82.2 26.1
2000kB 13.4 99.4 296.6
20000kB 1.2 97.1 3320.0

SOAP Provider

Non Persistent
Msg Size Msg Rate % CPU Busy CPU ms/msg
256b 11703.5 100.0 0.3
2kB 8561.6 100.0 0.5
20kB 2589.4 96.2 1.5
200kB 283.9 86.2 12.1
2000kB 26.4 84.3 127.9
20000kB 2.5 100.0 1606.4

ISO 8583 Transformation

Non Persistent
Msg Size Msg Rate % CPU Busy CPU ms/msg
120B 4502.5 97.2 0.9
134B 3207.2 96.7 1.2
1384B 2205.6 100.0 1.8

RESTful API – Post

Non Persistent
Msg Size Msg Rate % CPU Busy CPU ms/msg
256b 4589.5 99.4 0.9
2kB 2394.9 99.6 1.7
20kB 483.3 100.0 8.3

RESTful API – Get

Non Persistent
Msg Size Msg Rate % CPU Busy CPU ms/msg
256b 5508.7 98.6 0.7
2kB 3433.6 96.1 1.1
20kB 830.5 98.7 4.8

Measurement Environment

All throughput measurements where taken on a single server machine. The client type and machine on which they ran varied with the test. The details are given below.

Server Machine

The hardware consisted of:

  • LPAR on an IBM z13 consisting of 4 * 2964¬†processors
  • SAN comprising:
    • Brocade 8Gb 80 port switches
    • DS8800 storage system
  • 16GB RAM
  • 1GB Ethernet Card

The software consisted of:

  • z/OS 2.01
  • WebSphere MQ V7.1
  • IBM Integration Bus V10.0.0.2
  • DB2 V10

Client Machine

The hardware consisted of:

  • IBM xSeries x3550 M4 with 2 x Oct-Core Intel(R) Xeon E5-2680
  • 2.70GHz processors with HyperThreading turned on
  • One 135 GB SCSI hard drive formatted with NTFS
  • 32 GB RAM
  • 1 GB Ethernet Card

The software consisted of:

  • Microsoft Windows Server 2008 R2
  • WebSphere MQ V7.5.0.1
  • IBM Java V7

Network Configuration

The client and server machines were connected using a full duplex 1 Gigabit Ethernet LAN with a single hub.

Join The Discussion

Your email address will not be published. Required fields are marked *