Experience Analytics recommends cycling the services on all Processing Servers (Canisters) and Report Servers once per day during off-peak hours. By default, the Experience Analytics Scheduling Service is configured to run a cycle services job on each Experience Analytics server at 12:30am, local time. All Experience Analytics servers can be cycled at the same time. The Processing Servers and Reporting Servers are the most important ones to cycle daily.
If you deployed a Health-Based Routing server in your system, configure cycle services on the Processing Servers so that the HBR always has a Processing Server available to which to send hits. Otherwise, data might be lost.
Cycling services on a nightly basis alleviates the following issues:
- On the Processing Server, Canister services use much memory. At the end of the day, memory that is used for the Short-Term Canister can be highly fragmented and therefore less efficient. Recycling the services automatically defragments the Canister memory and ensures consistent performance in the Short-Term Canister.
- On the Processing Server, cycling services process also runs scripts through
TLTMaint.exeto verify the integrity of the Long-Term Canister.
- Cycling services flushes out any residual information about existing sessions and prepares the system for the next day.