The logs were clear: encoding jobs were missing deadlines, and the culprit was bad ramp contracts in FFmpeg.
FFmpeg ramp contracts define how operations scale over time, especially in pipelines that need to balance CPU use, memory, and I/O. When contracts are wrong, encoders stall or spike, leading to unpredictable throughput. In high-load systems, even small mismatches between requested resources and real utilization compound into failures.
A clean ramp contract ensures predictable job starts. It maps workload curves to available system capacity. In FFmpeg, this often means controlling thread counts, buffer sizes, and applying rate controls in sync with demand growth. Without this, jobs can flood the system during ramp-up, overwhelming transcoders or starving downstream processes.
Implementing correct ramp contracts in FFmpeg starts with profiling. Measure load patterns for your actual content mix, not synthetic benchmarks. Identify start-up latencies, codec-specific performance differences, and the interplay of filters with I/O throughput. Then set ramp parameters so load builds at a controlled pace—balancing speed with system stability.