Increase document conversion and fax documents HA replication efficiency
Starting from 2025.Spring.2 UCX release, two new settings are included in stonefax.default
file, both of them into [Settings]
section:
Concurrent documents conversion
DocumentConversionConcurrency
defines the number of concurrent running PrintUtility processes to convert fax documents.
The purpose of this setting is to customize CPU usage to avoid overhead due to conversion.
Changing this value requires restarting Digital Fax service.
Values
If set to 0 (default value), the number of concurrent PU corresponds to the number of CPU cores.
>0 and <1, the number of concurrent PU is equal to the number of CPU cores multiplied by this value.
>=1, the number of concurrent PU is exactly equal to the specified value.
Use dot as decimal separator.
At start-up, Digital Fax traces the configured timeout:
INFO { 5} [StoneFax] [SvFaxService] Document conversion concurrency: Total cores {4}, Desired concurrency {0}, Effective concurrency {4}
Example
Assuming the number of CPU cores is 16, if DocumentConversionConcurrency
is set to 0.25, the number of concurrent PU is 4 → 0.25 means 1/4 so 16/4.
Document unavailability timeout
Applied to an UCX Suite cluster only, DocumentUnavailableTimeoutInMinutes
is the maximum time in minutes to wait for the document to be replicated from the node which handles the fax document conversion to the other nodes in the HA cluster.
Once this timeout expires, the node tries to convert the fax document on its own using attachments instead of asking for it to other nodes.
Changing this value requires restarting Digital Fax service.
Default value is 5 (minutes).