Experiments considerations

When experiments are running in the store, the Scheduler launches a job that determines whether any of the current experiments have expired. The job simply compares the expiration date specified in the experiment, to the current system date. When an experiment is identified as expired, its status is updated in the database, and the experiment is prevented from displaying to customers.

By default, this job runs every 5 minutes. In extreme cases, it is possible that this job could require more than 5 minutes to complete, thus overlapping with the next scheduled instance of this job. The resulting impact can seriously affect system performance and thus, customer experience.

To reduce this possibility, you can increase the interval between the jobs. To change the time interval for the job, run the following SQL statement:

UPDATE SCHCONFIG 
    SET SCCINTERVAL = 1800 
    WHERE SCCPATHINFO = 'ExperimentCheckExpiry'

The SCCINTERVAL value defines the length of time, in seconds, before the job will be restarted.

 

Related Concepts

Performance
Experiments