Property Manager Name: Large File Optimization
The Large File Optimization feature improves performance and reliability when delivering large files. This behavior is required for objects larger than 1.8GB, and recommended for anything over 100MB. You should apply it only to the specific content to be optimized, such as a download directory’s .gz files, and enable the useVersioning option while enforcing your own filename versioning policy. Note that it is best to use NetStorage for objects larger than 1.8GB.
See also the largeFileOptimizationAdvanced behavior, which provides additional options for configuring partial object caching and HTTP/2 prefetching.
- enabled (boolean): Enables the file optimization behavior.
- enablePartialObjectCaching (enum string): Caches entire objects if set to NON_PARTIAL_OBJECT_CACHING. Otherwise when set to PARTIAL_OBJECT_CACHING, allows partial-object caching, which always applies to large objects served from NetStorage. To enable this, the origin must support byte-range requests.
- minimumSize (string): Optimization only applies to files larger than this, expressed as a number suffixed with a unit string such as MB or GB.
- maximumSize (string): Optimization does not apply to files larger than this, expressed as a number suffixed with a unit string such as MB or GB.
- useVersioning (boolean): When enablePartialObjectCaching is set to PARTIAL_OBJECT_CACHING, enabling this option signals your intention to vary filenames by version, strongly recommended to avoid serving corrupt content when chunks come from different versions of the same file.