You can configure the number of threads that the Archiver uses in order to tweak archiving performance and CPU load. By default, the Archiver is configured to 2 threads. If you feel that archiving is too slow, you may want to increase this value. If, instead, you feel that your CPU load is too high, you may want to decrease this value.
Procedure
- On the machine on which your Archiver runs, access its configuration location and open cd_archivemanager_conf.xml for editing.
- Find the
ArchiveQueue element and set one or more of the following attributes:
| Attribute | Description |
|---|
PollInterval | The amount of seconds that Archive Manager waits before checking the Archive Queue again. |
MaxThreads | The maximum number of processor threads made available for the Archive Queue. If left unspecified, this attribute defaults to the value 2. |
MaxRetries | The maximum number of times Archive Manager retries a transaction if it fails (due to a temporary database deadlock, for example). If left unspecified, this attribute defaults to the value 10. |
RetryWaitInterval | The amount of milliseconds that Archive Manager waits before retrying a failed transaction. If left unspecified, this attribute defaults to the value 100. |
When configuring the number of threads, bear the following in mind:
- A higher number of threads speeds up archiving but puts a heavier load on the CPU.
- A lower number of threads slows down archiving but burdens the CPU less.
- If you feel that you cannot find a middle ground between these two, consider scaling out the Archiver to its own machine.
- Save and close cd_archivemanager_conf.xml and restart the Web application to apply your changes.