kmp_cc_in_max_free_buffers

The `kmp_cc_in_max_free_buffers` directive sets the maximum number of free buffers available in the Kaltura Media Framework.

Syntaxkmp_cc_in_max_free_buffers number;
Defaultnone
Contextstream, stream server
Arguments1

Description

The kmp_cc_in_max_free_buffers directive is specifically designed for optimizing buffer management in the Kaltura Media Framework, which is utilized for streaming media. By defining the maximum number of free buffers, this directive helps in controlling memory usage, ensuring that the system does not exceed the allocated resources when handling streaming data. This can significantly improve the performance of the system, especially during high-load scenarios where numerous connections and media streams are being processed concurrently.

When this directive is employed within the stream or stream server contexts, it accepts a single integer value that dictates the upper limit of the free buffers available for incoming connections. The framework uses these buffers to temporarily hold data packets before they are processed or sent to their final destinations, making effective buffer management critical for maintaining optimal streaming performance. The behavior of the system will dynamically adapt based on this configuration, affecting both latency and throughput during media transmission.

It's important to note that setting this value too low may lead to unnecessary buffering and degraded streaming quality, while setting it too high could result in excessive memory consumption, thus requiring careful tuning based on the specific deployment circumstances. Administrators should monitor performance metrics to determine the most effective setting for their use case.

Config Example

stream {
    server {
        kmp_cc_in_max_free_buffers 1000;
    }
}

Setting the value too low can lead to increased latency due to insufficient buffer space.

Excessively high values can result in high memory consumption, impacting other processes on the server.

This directive only has an effect within the specified stream or stream server contexts.

← Back to all directives