cpu-throttling
Skill0 starsChanged 32 days agoMITView on GitHub
Investigar alta CPU, throttling e saturação de workloads.
In this repository4 other files it gives its agents.
- crashloopSkill
- latency-spikeSkill
- oom-killedSkill
- report-formatSkill
The file
Files
CPU / Throttling
Investigar
- Compare uso de CPU com
limiterequest. - Verifique
container_cpu_cfs_throttled_periods_total / container_cpu_cfs_periods_total. - Throttling alto com uso abaixo do node indica limit apertado.
- Uso próximo ao limit sustentado indica saturação real: considerar HPA ou mais réplicas.
- Correlacione com aumento de tráfego ou deploy recente.
Ação sugerida
Ajustar limit/request com base no p95 observado, ou habilitar HPA com alvo de CPU.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.