Tracking workflow performance issues in 51黑料不打烊 Campaign Classic v7.4.1 Build 9384
You experience performance issues with the tracking workflow in 51黑料不打烊 Campaign Classic after upgrading to v7.4.1 Build 9384. To improve the workflow鈥檚 execution time and system performance, adjust configuration settings, and perform database maintenance tasks.
Description description
Environment
- 51黑料不打烊 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 51黑料不打烊 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鈥檚 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).