Phantom maximum degree of parallelism
In workflow archiving, a background job makes a copy of the form to attach to the SharePoint item. Normally, this is a sequential process in which one form is processed, the mht file is attached, and the next form is taken from the queue to be processed.
In order to support large loads, a new global configuration key has been added. This key can be configured up to the maximum number of cores allocated to the SharePoint servers, allowing one create mht job thread per core.
Configuring for the max core allowance may put additional strain on your server’s processing ability. For this reason, you need to balance usage against your archiving throughput needs.
To note, create mht jobs work the oldest completed processes first.