large_file_optimization_advanced
- Property Manager name: Large File Optimization (Advanced)
- Behavior version: The
v2024-10-21
rule format supports thelarge_file_optimization_advanced
behavior v1.0. - Rule format status: GA, stable
- Access: Read-only
- Allowed in includes: Yes
The Large File Optimization feature improves performance and reliability when delivering large files. You need this behavior for objects larger than 1.8GB, and it's 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. Note that it is best to use NetStorage for objects larger than 1.8GB.
This advanced behavior provides additional HTTP/2 options not present in the large_file_optimization
behavior.
Option | Type | Description | Requires | |
---|---|---|---|---|
enabled | boolean | Enables the file optimization behavior. | {"displayType":"boolean","tag":"input","type":"checkbox"} | |
object_size | string | Specifies the size of the file at which point to apply partial object (POC) caching. Append a numeric value with a | {"displayType":"string","tag":"input","type":"text"} {"if":{"attribute":"enabled","op":"eq","value":true}} | |
fragment_size | enum | Specifies the size of each fragment used for partial object caching. | {"displayType":"enum","options":["HALF_MB","ONE_MB","TWO_MB","FOUR_MB"],"tag":"select"} {"if":{"attribute":"enabled","op":"eq","value":true}} | |
Supported values: FOUR_MB HALF_MB ONE_MB TWO_MB | ||||
prefetch_during_request | number | The number of POC fragments to prefetch during the request. | {"displayType":"number","tag":"input","type":"number"} {"if":{"attribute":"enabled","op":"eq","value":true}} | |
prefetch_after_request | number | The number of POC fragments to prefetch after the request. | {"displayType":"number","tag":"input","type":"number"} {"if":{"attribute":"enabled","op":"eq","value":true}} |
Updated 17 days ago