WebSphere Message Broker, Version 8.0.0.7 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

Performance planning

When you design your broker environment, and the resources associated with the brokers, decisions that you make can affect the performance of your brokers and applications.

Message flows
A message flow includes an input node that receives a message from an application over a particular protocol; for example, WebSphere® MQ. The message must be parsed by the input node, although some parsers support partial parsing which might reduce processing, because only the parts of the message that are referenced are parsed. Other processing in a message flow that might affect performance are the amount, efficiency, and complexity of ESQL, access to databases, and how many message tree copies are made.

You must consider how you split your business logic; how much work should the application do, and how much should the message flow do? Every interaction between an application and a message flow involves I/O and message parsing, and therefore adds to processing time. Design your message flows, and design or restructure you applications, to minimize these interactions.

For more information about these factors, see Optimizing message flow response times and Optimizing message flow throughput.

Messages and message models
The type, format, and size of the messages that are processed can have a significant effect on the performance of a message flow. For example, if you process persistent messages, they have to be stored for safekeeping.

You might need to process messages with a well-defined structure; if so, you can create DFDL models for your messages. If you do not plan to interrogate the structure, you can work with undefined messages, such as BLOB messages.

If you are working in XML, be aware that it can be verbose, and therefore produce large messages, but XML message content is easier to understand than other formats, such as CWF. Field size and order might be important; these factors can be included in your DFDL model.

For more information about these factors, see Optimizing message flow response times and Performance considerations for regular expressions in TDS messages.

Broker configuration
You can create and configure one or more brokers, on one or more computers, and for each broker you can create multiple execution groups, and multiple message flows. Your configuration decisions can influence message flow performance, and how efficiently messages can be processed.

For more information about these factors, see Tuning the broker, and Optimizing message flow throughput.

All these factors are examined in more detail in the Designing for Performance SupportPac (IP04).

For a description of common performance scenarios, review Troubleshooting performance problems.

For further articles about WebSphere Message Broker and performance, review these sources:

Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2016Copyright IBM Corporation 1999, 2016.

        
        Last updated:
        
        Last updated: 2016-05-23 14:47:00


Task topicTask topic | Version 8.0.0.7 | ae24000_