Hi! On Thu, Jun 26, 2025 at 05:01:39PM +0000, Krystian Kazmierczak (Nokia) via Gcc-help wrote: > I'd like to continue this topic. The context of that is that I am testing distcc to perform distributed compilation across many hosts which are in fact pods (containers) in k8s env. What I observe is that when all compilation which run on certain container cause memory pressure (memory utilization hits memory limit defined by cgroupv2 for container, swap is disabled) There's your problem. Self-inflicted wound. Swap space is required on Linux systems for it to behave well at all under memory pressure. It was true in 1991, it still is true today. Here's Red Hat's documentation for this: https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/7/html/storage_administration_guide/ch-swapspace Segher
