vod_max_mapping_response_size
The `vod_max_mapping_response_size` directive sets the maximum response size for asset mapping in the NGINX-based VOD Packager module.
Description
The vod_max_mapping_response_size directive is used within the NGINX configuration to define an upper limit on the response size for assets that are being mapped during video on demand (VOD) processing. This is particularly useful in scenarios where large media files are being handled, allowing administrators to control memory usage and response times by limiting the data sent in a single response. By specifying the maximum mapping response size, NGINX can ensure that it does not exceed available memory, and improve handling of client requests by avoiding excessively large data transfers.
When this directive is set, it binds an integer value representing the maximum byte size of the response that can be sent during mapping operations. If a request exceeds this limit, NGINX may either truncate the response or return an error, depending on the surrounding configuration. The directive can be placed in various contexts such as http, server, or location blocks, enabling flexible configuration tailored to specific needs. It is essential to consider the nature of the content being served and the expected user traffic when configuring this directive, as inappropriate values can impede service quality for end-users.
Properly utilizing the vod_max_mapping_response_size directive contributes to efficient resource management, potentially allowing servers to handle higher loads without degrading performance. This is especially relevant in environments where multiple video streams are accessible simultaneously, requiring careful balancing of resource consumption across concurrent requests.
Config Example
http {
vod_max_mapping_response_size 1m;
server {
location /video/ {
# other VOD configurations
}
}
}Setting the value too low may cause legitimate requests to fail.
Ensure that the specified size is appropriate for the average size of your video files to avoid unnecessary truncation.
Changes to this directive may not take effect without reloading the NGINX configuration.