Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

bug: CPU usage misses other processes that share the same CPU limit (cgroup v2)

Aperta
  • Qualcosa non va?
#41 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

@DanielleMaywood ci sta già lavorando.

Dal 23/10/2026.

  • #42 di @DanielleMaywood — aperta
  • #43 di @david-fraley — aperta

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
67/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
go, linux
Ambito
observability

Direzione di ricerca

Read the CPU limit and usage handling behind ContainerCPU(), then compare it with the memory cgroup selection described in #39. Update CPU usage selection to use the cgroup with the applicable limit, and check that usage remains unchanged when the process cgroup has the limit or no limit exists. The expected reproduction is about 4.3/12 cores (36%) in the reported nested cgroup setup.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Summary

This is the CPU version of #38.

clistat gets the CPU limit from the nearest parent cgroup that has one. But it reads CPU usage from the process's own cgroup. Other cgroups under that parent use the same limit, but their usage is not counted. So clistat can show the container as almost idle when it is busy.

This often happens when a container runs other containers inside it. The process is in /init.scope and the inner containers are in /docker/<id>. Both are under the container root, which has the limit.

Why this is wrong

  • A cgroup's cpu.stat includes CPU time from all cgroups below it. In the kernel, each cgroup's CPU time is added to its parent's (cgroup_base_stat_flush() in kernel/cgroup/rstat.c, v6.17). If you only want a cgroup's own time, there is a separate file, cpu.stat.local.
  • A limit in cpu.max applies to the cgroup and everything below it (cgroup v2 docs).

So to see how close we are to the limit, we must read usage from the cgroup that has the limit.

How to reproduce

We used a sysbox container on cgroup v2. The container root has a 12-core limit (cpu.max is 1200000 100000). /init.scope has no limit, and the process is in /init.scope. Then we ran 4 busy loops in an inner container:

docker run -d --name cpuhog alpine sh -c 'for i in 1 2 3 4; do (while :; do :; done) & done; wait'
What we measured (over 2 seconds) Cores used
Container root 4.3
/docker 4.01
/init.scope 0.01
ContainerCPU() on main (a2db32a) 0.009/12 cores (0%)

What should happen

clistat should show about 4.3/12 cores (36%).

How to fix it

Do the same thing #39 does for memory. Find the cgroup that has the CPU limit, then read CPU usage from that same cgroup. If the process's own cgroup has the limit, or there is no limit, nothing changes.

The nearest limit is not always the one that matters. That is a separate problem, covered in #40.

Generated by Coder Agents on behalf of @DanielleMaywood.

Lingua principale
Go
Stelle
11
Fork
2
Merge medio
2g 21h
PR unite (30g)
1

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di coder/clistat

Tutte le issue di coder/clistat

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.