Processing large images in Assets Server – Home

Info: This feature requires Assets Server 6.77 or higher.

Processing large images (containing hundreds of megapixels) requires a lot of memory and disk space. Running such a process can potentially result in the processing node running out of disk space or ending up processing infinitely.

To prevent such situations, the maximum disk space and memory used for processing a file can be configured through the following options in the cluster-config.properties.txt file:

processingMemoryLimit. For setting the maximum memory (in GiB) used by ImageMagick and GraphicsMagick. The default value is 1GiB.

Example: processingMemoryLimit=1GiB

Notes:

Leave empty to use unlimited memory; this may result in server slowdowns or failures when all free memory runs out.
Files exceeding the limit during processing are written to disk.
Calculate the proper memory limit for your system by dividing the available free memory by the processing capacity (processing.queue.capacity configuration property, by default equal to number of CPU cores plus one).
Requires a restart of Assets Server.

processingDiskspaceLimit. For setting the maximum disk space (in Gib) used by ImageMagick and GraphicsMagick when processing large files (over 2 Gigabyte during processing). The default value is 8GiB.

Example: processingDiskspaceLimit=8GiB

Notes:

Leave empty to use unlimited disk space; this may result in server failures when running out of disk space.
Make sure that the system has enough free disk space for the temporary folder (usually /var/tmp) to contain processingDiskSpaceLimit multiplied by the processing capacity.

Notes

For files that exceed the sum of both limits, no preview or thumbnail is generated.

Notes

Related articles