Documentation Center

When to scale out your Archiver

Asynchronous archiving speeds up deployment but puts a heavier load on the machine on which your Content Deployer runs. If this load becomes too high, scaling out the Archiver becomes an option to consider.

In order to make sure that its archiving activities do not get in the way of publishing (deployment) of content, Archive Manager performs its archiving asynchronously, that is, separate from deployment. This ensures that the Content Deployer does not need to wait for the archiving to finish before it can put its content online.

The drawback of this approach is that archiving may still be going on while a new deployment is attempted. If publish actions are frequent and/or large in size, the CPU load on the machine that runs Content Deployer may become too big.

You can mitigate against this by tweaking the number of threads used by Archive Manager (scaling down): the lower the number of threads, the lower the CPU loads. Failing that, you can invest in a faster machine.

But if the CPU load still remains too high, another option is to install the Archiver (the part of the Modules that does the 'heavy lifting') on its own on a separate machine. You can then configure the Archive Manager Modules to stop calling its own, built-in Archiver, and to call this remote Archiver instead.