Feature cost considerations

Be aware that each optional feature or function you add causes additional resource and CPU costs.

For best results, consider which features you need. Then, decide whether you want to run each feature all the time or if you can save CPU costs and turn the feature on only when needed.

Following are additional tips for deciding which optional features and functions to add:

• Monitor traces for real-time are typically inexpensive. This includes Statistics and Accounting class (1) traces.
• Accounting trace class (3) and especially class (2) on the plan level as well as the equivalent classes (7 and 8) on the package level will generate additional overhead within the DB2 engine.
• SQL related traces (Dynamic SQL, NegSQL, sort, scan, and locking) can be very expensive. These traces should be used cautiously and only for a short period of time. For example, they are used as an option in Near-Term History.
• Object Analysis can be very expensive. Consider using the online function to switch this function on and off dynamically if you need it.