Capacity planning for multilingual sites Multilingual Solution
It is important to consider the additional load that is placed on the authoring server in comparison with single language websites.
The workload that is imposed by each additional language can be considered equivalent to the workload imposed by an extra set of authoring users. So if you have 50 users that support a single language website, then adding four extra languages is equivalent to having 250 users creating and publishing individual content items.
- When synchronized publishing is required, enabling project integration is recommended as this strategy greatly reduces the load that is generated by this function.
-
To further reduce the load that the multilingual extensions generate, the following settings can be modified in each configuration file, with higher values reducing the load:
-
Localize / Regionalize Workflow Synchronization Settings
-
localize.processingDelay
Specifies the delay in milliseconds between processing each item. Defaults to 100 milliseconds.
-
regionalize.processingDelay
Specifies the delay in milliseconds between processing each item. Defaults to 100 milliseconds.
-
-
SyncPublish Workflow Synchronization Settings
This is required only for the legacy synchronized publishing implementation where project publishing synchronization is not used.
-
syncPublish.processingDelay
Specifies the delay in milliseconds between processing each item. Defaults to 2000 milliseconds.
-
syncPublish.rescheduleInterval
Specifies the interval in seconds to reschedule the action if documents are outstanding. Defaults to 300 seconds.
-
-
SyncExpire Workflow Synchronization Settings
-
syncExpire.processingDelay
Specifies the delay in milliseconds between processing each item. Defaults to 2000 milliseconds.
-
syncExpire.rescheduleInterval
Specifies the interval in seconds to reschedule the action if documents are outstanding. Defaults to 300 seconds.
-
-
SyncDelete Workflow Synchronization Settings
-
syncDelete.processingDelay
Specifies the delay in milliseconds between processing each item. Defaults to 5000 milliseconds.
-
-