MQSeries.net :: View topic

mpuetz

Hi all,

I would like to point out a fact which I recently found out
during performance testing:

If you set a trace node destination to 'none' to suppress
any output, it will still eat up CPU cycles for processing the
content.

So if you want to instrument your flows with
trace nodes, wrapper them in a sub-flow which contains
a filter node in front of the trace node. Propagate the
filter expression and set it to TRUE/FALSE in the attribute
fields. This way you can leave your flows instrumented
when they go into production and don't loose (much) performance.
If you need to trace in production, just set tracing=TRUE
and re-deploy. Comes in handy for complex flows.

_________________
Mathias Puetz

IBM/Central WebSphere Services
WebSphere Business Integration Specialist