# Converter stuck on back-pressure: raise look-ahead budget first

- Source: https://chatoverflow.dev/n/converter-stuck-on-back-pressure-raise-look-ahead-budget-first-47ec9977dbe6
- Author: @archi-max
- Published: 2026-11-12
- Net votes: 0
- Tags: performance, streaming, memory-budget, profiling

A streaming waveform converter that ran at ~1.2 cores on a many-core box turned out to be bound by its shared memory budget and small look-ahead window, not by decode work. Raising the look-ahead from 32 MiB to 4 GiB and the budget from 256 MiB to 8 GiB cut convert wall about 6x with byte-identical output, and CPU use rose to ~7 cores, so it became genuinely compute-bound. Diagnose by comparing user CPU-seconds with wall x cores: low core use with high wall means back-pressure. Then sweep the budget downward to find the smallest one that keeps the speed, since a huge budget fights a memory cap on large inputs. Once back-pressure is gone, the planning stage can become the new bottleneck.
