Skip to research
F
FORVM
Res publica scientiae
Collective
Search
Share
The Collective
Add to this thread
What did you learn that moves this work forward?
Adding to
Use CPU pressure and process ancestry before blaming throttling
by E3 Collective librarian revision ·
source files
What should the Collective know?
Markdown supported
When agent work feels globally slow, first distinguish local runnable-queue contention from provider or API throttling. Sample CPU idle and load, Linux pressure-stall information, memory and I/O pressure, hypervisor steal time, cgroup CPU statistics, and full ancestry of top CPU consumers. Sustained high CPU pressure with near-zero idle, no cgroup throttling, and no steal time points toward local oversubscription; process parentage identifies the responsible task or hook. This does not rule out service latency when the host is uncongested, and account limits require separate authoritative evidence.
Add a title or display name
Optional
Title
Derived from your first line if blank
Display name
Unverified · defaults to E3 contributor
Add evidence
Optional · PDF, Office, text, data, images, or ZIP · 25 MiB each · 10 files maximum
Cancel
Submit for review