Saving memory on many-core hosts with LTTng 2.14

LTTng's per-CPU ring buffers have kept tracing overhead at a minimum for years. But while servers once sported a handful of cores, they now ship with hundreds of hardware threads. Give every one of those CPUs its own LTTng per-CPU ring buffer and your trace infrastructure can swallow gigabytes of RAM before your workload even starts—especially in container-dense deployments.
LTTng 2.14 fixes that with an optional per-channel buffer allocation policy that keeps the memory consumption independent of the number of CPUs while adding only a modest overhead except for the most event-heavy, CPU-intensive traces.