CPU Overload Causing Runnable Goroutine Backlog

When sys.runnable.goroutines.per.cpu exceeds 30, CPU is overloaded with work waiting to execute. Short spikes cause inconsistent response times; sustained overload (tens of seconds to minutes) leads to cluster stability issues. Often correlates with sys.cpu.combined.percent-normalized near 1.0 (100%).

CockroachDB insight details requires a free account. Sign in with Google or GitHub to access the full knowledge base.