Tuning the performance impact of application activity trace

Enable application activity trace can incur a performance penalty. This can be reduced by only tracing the applications that we need, by increasing the number of applications draining the queue, and by tuning ActivityInterval, ActivityCount and TraceLevel in mqat.ini.

About this task

Enable application activity trace selectively for an application or for all queue manager applications can result in additional messaging activity, and in the queue manager requiring additional storage space. In environments where messaging performance is critical, for example, in high workload applications or where a service level agreement (SLA) requires a minimum response time from the messaging provider, it might not be appropriate to collect application activity trace or it might be necessary to adjust the detail or frequency of trace activity messages that are produced. The preset values of ActivityInterval, ActivityCount and TraceLevel in the mqat.ini file give a default balance of detail and performance. However, we can tune these values to meet the precise functional and performance requirements of our system.

What to do next

The simplest way to view the contents of application activity trace messages is to use the amqsact sample program.

Parent topic: Configure central collection of application activity trace information