Changes to Web tracking configuration

The following properties have been added to Tridion.Aggregation.config for Web tracking:

  • the maxThreads setting has been renamed maxAggregationThreads (mandatory)—the number of threads used to aggregate tracked data. Each batch is split into into equal parts and each part is processed in its own thread. The minimum value is 1, and it is recommended to set the maximum value to no greater than the number of cores on the server. You can limit the number of cores that Aggregation service uses by setting this value.
  • maxAggQueueLength (optional)—the maximum number of work items in the aggregation queue. If aggregation is slow, do not set maxAggQueueLength too high because batches will start to experience timeout failure on the synchronization server. The default value is 4, and the minimum value is 1:
  • heartbeatTimeout—the heartbeat timeout of the Aggregation service. Specify optionally the hours, minutes and seconds using the format: 12h34m56s. You can omit the s for seconds, in which case 60 for example is interpreted as 60 seconds.
The following is an example of the Tridion.Aggregation.config settings:
<settings aggregationInterval="30" maxAggregationThreads="2" maxAggQueueLength='4' heartbeatTimeout='2m' />