Webtrends administrators can change Score settings to improve performance. If you use Webtrends On Demand, or if you need additional help with Score performance, please contact Support.
The FrequencySeconds and MaxProcessMinutes parameters determine how much data Score can process:
- The FrequencySeconds parameter in the wt_ProfileAddOnModule table in the wt_Sched database determines how often the Scheduler initiates scoring.
- The MaxProcessMinutes parameter in Webtrends Installation Directory\modules\Score\wtscore.ini file determines the number of minutes of data Score processes each time scoring occurs.
For example, if the Scheduler starts the Score Engine every 30 minutes, and the MaxProcessMinutes parameter is set to 60, Score attempts to process 60 minutes of data every 30 minutes. In other words, two hours of visit data will be scored every hour.
Number and Type of Rules
The time required to compute scores for a rule set depends on the number and type of rules configured. The more rule sets you define for a profile, the more time scoring will take to complete. Selecting hundreds of products in a Product View rule increases the time Score takes to process the rule. Also, some rule types, such as Scenario rules, take longer to process (a rule set should not contain more than two Scenario rules). If scoring begins to take longer than the FrequencySeconds interval, it is falling behind in processing. In this case, you should lower the MaxProcessMinutes setting until scoring can catch up. Alternatively, you can disable some rules or rule sets to reduce processing time.
Scoring and the Event Database Loader
For best performance, you should integrate scoring with the data processing schedule of the Event Database Loader. As a best practice, Score should always be able to process more data than the Event Database Loader can load. This ensures that Score can continue to score visits as they are loaded and also provides a cushion for re-scoring historical data. Because re-scoring visits (as after modifying a rule set) uses the same batch window as current scoring, and historical data is scored first, your settings should enable Score to catch up if re-scoring of historical data is required.
As a general guideline, you should run Score more frequently than the Event Database Loader, using a batch window 2-5 times larger than the window of visits loaded by the Event Database Loader. In the example above, if the Event Database Loader runs every 30 minutes and loads 30 minutes of visit data, you should set FrequencySeconds to 300-600 seconds (every 5-10 minutes) and MaxProcessMinutes to 60-180 minutes.