How onimekh/oci-cpu-balancer works
This repository provides an OCI CPU balancer and a separate watchdog. The main runtime loop aims to keep system CPU utilization within a configured range while yielding to real workloads; an hourly watchdog can restart a manually stopped service after 24 idle hours. The README describes the service, timer, configuration, scheduling policy, and memory cap, but no source excerpts were supplied, so the graph shows only documented relationships.
Main entry points: oci-cpu-balancer CPU balancer · oci-cpu-balancer.service Balancer service · oci-cpu-watchdog Watchdog · oci-cpu-watchdog.service Watchdog service
Components 11
CPU control
- Balancer config
oci-cpu-balancer.conf - CPU balancer
oci-cpu-balancer
Watchdog
- Watchdog
oci-cpu-watchdog - Watchdog service
oci-cpu-watchdog.service - Hourly timer
oci-cpu-watchdog.timer
Host runtime
- Balancer service
oci-cpu-balancer.service - Linux scheduler
- Host CPU usage
Other components
- Operator
- Host workloads
- systemd
Connections 10
- Balancer config → CPU balancer: configures
README.md - Balancer service → CPU balancer: runs
README.md - CPU balancer → Host CPU usage: maintains target
README.md - CPU balancer → Linux scheduler: runs idle priority
README.md - Host workloads → Linux scheduler: preempts burners
README.md - Hourly timer → Watchdog service: triggers hourly
README.md - Watchdog service → Watchdog: runs
README.md - Watchdog → Balancer service: restarts when idle
README.md - systemd → Balancer service: caps memory
README.md - Operator → systemd: manages services
README.md