Consultor Eletrônico

SUMMARY:

This solution applies to Progress SonicMQ, all versions.
There are many factors which can affect the performance (typically
measured in messages/second) of SonicMQ.

EXPLANATION:

These factors include:

Platform:
- Machine, OS
- JRE (vendor, version)
- Number of processors
- Processor speed
- Amount of available memory
- I/O subsystem (disk, controller)

Messaging configuration:

- Messaging model - Point-to-Point or Publish/Subscribe
(pub/sub)?

- If pub/sub, durable or non-durable subscriptions, and if
durable, are there any disconnected durable subscribers?
Messages for disconnected durable subscribers are written
to disk.

- Message delivery mode - Persistent or non-persistent?
Persistent messages are written to disk.

- Are sessions transacted?
Information on open transactions is written to disk.

- Is security enabled?

- Number of clients

- Client configuration - clients on separate machines?

- Message size

- Message type - Text, Object, Map, Stream, Bytes, or XML?

Although the effect of message type on performance may be
neglible when compared with the other factors listed
here, parsing XML into a DOM document tree can be
expensive in terms of performance, and processing an
Object message can take longer than processing other
message types.

Text, Map, and XML messages also must be converted to
UTF. This conversion takes processing time, and the
resulting message is larger than the original.

The test itself:
- How is throughput being measured, for example:
Number of messages sent per second?
Number of messages sent and received?

- Does the test do any screen or disk I/O?
I/O can slow throughput considerably, to the point
of making the test invalid.


References To Written Documentation:

SonicMQ Installation and Administration Guide, Platform Requirements

SonicMQ Release Notes, Requirements

SonicMQ Supported Products & Platforms:
http://www.sonicsoftware.com/products/platforms.htm