WebLogic Server Performance and Tuning
For WebLogic Server releases 9.0 and higher, JMS provides advanced store-and-forward capability for high-performance message forwarding from a local server instance to a remote JMS destination. See Understanding the Store-and-Forward Service in Configuring and Managing WebLogic Store-and-Forward.
Window Sizefor applications that handle small messages. By default, a JMS SAF agent forwards messages in batches that contain up to 10 messages. For small messages size, it is possible to double or triple performance by increasing the number of messages in each batch to be forwarded. A more appropriate initial value for
Window Sizefor small messages is 100. You can then optimize this value for your environment.
Note: Changing the
Window Size for applications handling large message sizes is not likely to increase performance and is not recommended.
Window Size also tunes WS-RM SAF behavior, so it may not be appropriate to tune this parameter for SAF Agents of type
Window Interval. By default, a JMS SAF agent has a
Window Intervalvalue of 0 which forwards messages as soon as they arrive. This can lower performance as it can make the effective
Window sizemuch smaller than the configured value. A more appropriate initial value for
Window Intervalvalue is 500 milliseconds. You can then optimize this value for your environment. In this context, small messages are less than a few K, while large messages are on the order of tens of K.
Note: Changing the
Window Interval improves performance only in cases where the forwarder is already able to forward messages as fast as they arrive. In this case, instead of immediately forwarding newly arrived messages, the forwarder pauses to accumulate more messages and forward them as a batch. The resulting larger batch size improves forwarding throughput and reduces overall system disk and CPU usage at the expense of increasing latency.
Non-Persistent QOSvalue to
At-Least-Oncefor imported destinations if your application can tolerate duplicate messages.