In addition to the space necessary to install the software, Image Serving has the following disk space requirements:
Description/ Default Location/ Set With | Calculation/ Recommendation | Comments |
---|---|---|
Source images, fonts, ICC profiles install_folder /images IS::RootPaths |
Varies; see comments below. |
Only needs to be accessible to the Image Server; the servers never modify data. |
HTTP response data cache install_folder /cache/is-response PS::ResponseCacheFolders |
PlatformServer::cache.maxSize x 2; at least 2 GB recommended. |
This cache also stores nested/embedded data and foreign source images. |
Image catalog data cache install_folder /cache/catalog CS::CatalogCacheFolder |
Allow the catalog folder to use 1.5x the space. |
Populated when catalogs are loaded initially. |
Log data install_folder /logs PS::LogFolder IS::LogFile SV::LogFile |
100 Mbytes or more. |
Varies depending on logging configuration and server use. |
Image Server temporary files install_folder /temp IS::TempDirectory SV::TempDirectory |
100 MBytes is sufficient for most uses. |
Short-lived data; may be needed for source images other than PTIFFs and certain response image formats. |
It is recommended to convert all source images to the pyramid TIFF file format (PTIFF) using the Image Converter command-line tool (IC). This conversion ensures optimal runtime performance of Image Serving for all applications. While the Image Server can process all source file formats accepted by IC, Dynamic Media does not provide support for such uses.
When you use PTIFF files, the following rules of thumb can help you determine the space requirements.
total_space
(bytes) = number_of_images
x(2000 + avg_pixel_count
x avg_num_components
x p_factor
)
avg_pixel_count
The average pixel size (width x height) of all original source images. For example, if the original images are typically around 2k x 2k pixels, this would be 4M pixels.avg_num_components
Depends on the type of images. For mostly RGB images it is 3, for mostly CMYK or RGBA images it is 4. Use 3.5 if half the images are RGB and the other half is RGBA.p_factor
Depends on the compression type and quality set when the images are converted with IC.PTIFF compression | p_factor |
---|---|
Uncompressed |
33 |
Deflate-Compression |
25-0.75, depending on the image |
JPEG Compression |
1 (typical for JPEG quality 95) |
This approximation does not account for file system overhead. The actual space on disk may be substantially larger.
Example
An Image Serving deployment expects to use 30,000 low-resolution legacy images, with an average size of 500x500 RGB pixels. New print-quality image data is expected to be added at a rate of 10,000 per year. The typical CMYK image size is 4k x 6k bytes. All data is JPEG compressed at high quality. The total amount of disk space after 3 years of use is estimated as follows:
total_space
= 30,000 x (2k + 0.5k x 0.5k x 3 x 0.1) + 3 x 10,000 x (2k + 4k x 6k x 4 x 0.1) = 2.2 G + 268 GB = approximately 270 GB
For guaranteed best quality, deflate (zip) compression could be employed. Assuming a p_factor
of 0.4, the total amount of disk space required is approximately 4 times larger. In this case, slightly more than 1 TB.