Tracking workflow performance issues in ÃÛ¶¹ÊÓƵ Campaign Classic v7.4.1 Build 9384
You experience performance issues with the tracking workflow in ÃÛ¶¹ÊÓƵ Campaign Classic after upgrading to v7.4.1 Build 9384. To improve the workflow’s execution time and system performance, adjust configuration settings, and perform database maintenance tasks.
Description description
Environment
- ÃÛ¶¹ÊÓƵ Campaign Classic v7
- Console Build 9384, Server Build 9384
- Database: Oracle
Issue/Symptoms
The tracking workflow execution time increases after upgrading to v7.4.1 Build 9384. Performance degradation affects tracking information.
Resolution resolution
Note: The tracking workflow must be stopped before making configuration changes and restarted afterward to apply the new settings.
-
Adjust configuration settings by creating a new
NmsRecomputeDeliveryStats_BatchSizeoption. Navigate to Administration>Platform>Options in the ÃÛ¶¹ÊÓƵ Campaign Classic console. Change the batch size value from its default (e.g., 600) to a lower value such as 100. This change reduces the load on the system during the tracking workflow execution. -
Perform defragmentation and index rebuilding on key tables involved in the tracking process. These tables include
nmsdelivery,nmsrecipient,nmsdeliverylogstats,nmstrackingstats,nmstrackinglogrcp, andnmsbroadlogrcp. They are critical for tracking data and their performance can significantly impact the workflow execution time.- Ensure that table fragmentation is below a threshold of 30%. Use database management tools to check and reduce fragmentation.
- Rebuild indexes with fragmentation ratios over specified thresholds (e.g., over 30%) to improve query performance.
-
After implementing the changes, monitor the tracking workflow’s execution time:
- Use system monitoring tools to track the execution time of the tracking workflow.
- Confirm improvements by checking if hourly executions complete within acceptable timeframes (e.g., under 45 minutes).