Filed Oct 24, 03:53 IST; labelled compiler/runtime; no CL yet. The reporter runs kube-apiserver on 192-core AMD Genoa/Turin hosts with GOMAXPROCS unset, GOGC=400, 325k goroutines and 116β140 GB live heaps. GC cycles forced by the 2-minute timer took about 5.5 s on average. Cycles triggered by heap growth, which also enlist idle-mark workers on every core, took 14.8β20.6 s, and 18 of 20 marks ran past 9 s. During those marks, allocating goroutines (3β5 GB/s) sat parked in gcParkAssist, stalling etcd watches and the decrypt/decode path. In a 60 s profile, getempty β lfstack.pop β Cas64 took 33% of CPU-seconds, mostly reached from goroutine stack scanning. Porting arm64's existing lfstack backoff (CL 654895) to amd64 fixed it: 0 of 9 heap-triggered cycles stalled, marks took 5.0β7.2 s, and idle-mark CPU fell from a median of about 1,900 to about 430 CPU-s per cycle. A pause value of 8 (about 143 ns on Genoa) worked best. arm64's value of 128 is about 18x longer in wall time on amd64. The issue includes a standalone reproducer (r7a.48xlarge, 500k parked goroutines, 32 GB live heap). Longer term, #81304 would make the procyield argument mean the same thing on every architecture.
GODEBUG=gctrace=1).