Messaging Performance Configuration Parameters

Tuning WebLogic JMS 14-25 In response to changes in message rate and other factors, these algorithms change batch sizes and delivery times. However, it isnt possible for the algorithms to optimize performance for every messaging environment. The Messaging Performance Preference tuning option enables you to modify how these algorithms react to changes in message rate and other factors so that you can fine-tune the performance of your system.

14.17.1 Messaging Performance Configuration Parameters

The Message Performance Preference option includes the following configuration parameters: It may take some experimentation to find out which value works best for your system. For example, if you have a queue with many concurrent message consumers, by selecting the Administration Consoles Do Not Batch Messages value or specifying 0 on the DestinationBean MBean, the queue will make every effort to promptly push messages out to its consumers as soon as they are available. Conversely, if you have a queue with only one message consumer that doesnt require fast response times, by selecting the consoles High Waiting Threshold for Message Batching value or specifying 100 on the DestinationBean MBean, then the queue will strongly attempt to only push messages to that consumer in batches, which will increase the waiting period but may improve the servers overall throughput by reducing the number of sends. For instructions on configuring Messaging Performance Preference parameters on a standalone destinations, uniform distributed destinations, or JMS templates using the Administration Console, see the following sections in the Administration Console Online Help: ■ Configure advanced topic parameters ■ Configure advanced queue parameters ■ Uniform distributed topics - configure advanced parameters Table 14–4 Message Performance Preference Values Administration Console Value MBean Value Description Do Not Batch Messages Effectively disables message batching. Available messages are promptly delivered to consumers. This is equivalent to setting the value of the connection factorys Messages Maximum per Session field to 1. Batch Messages Without Waiting 25 default Less-than-full batches are immediately delivered with available messages. This is equivalent to the value set on the connection factorys Messages Maximum per Session field. Low Waiting Threshold for Message Batching 50 Wait briefly before less-than-full batches are delivered with available messages. ` Medium Waiting Threshold for Message Batching 75 Possibly wait longer before less-than-full batches are delivered with available messages. High Waiting Threshold for Message Batching 100 Possibly wait even longer before less-than-full batches are delivered with available messages. 14-26 Performance and Tuning for Oracle WebLogic Server ■ Uniform distributed queues - configure advanced parameters ■ Configure advanced JMS template parameters For more information about these parameters, see DestinationBean and TemplateBean in the Oracle WebLogic Server MBean Reference.

14.17.2 Compatibility With the Asynchronous Message Pipeline