free-my-cpulisted

# Free My CPU ## Core Rule Prefer a read-only audit before changing anything. Separate CPU saturation from I/O wait, memory pressure, blocked tasks, noisy dashboards, and runaway containers. Classify findings by safety and impact before recommending restarts, rate limits, query changes, or container resource caps. Never kill processes, restart services, edit crontab/systemd timers, change Docker Compose limits, or throttle production workloads unless the user explicitly accepts the exact target and impact. ## Quick Audit Detect the platform and pressure first: ```bash uname -a uptime nproc free -h cat /proc/pressure/cpu 2>/dev/null || true cat /proc/pressure/io 2>/dev/null || true ``` For Ubuntu/Linux, run the bundled read-only script first when possible: ```bash bash scripts/audit_linux_cpu.sh ``` For macOS, there is no bundled cleanup script yet; start with read-only built-ins: ```bash uptime sysctl -n hw.ncpu vm_stat top -l 1 -o cpu -stats pid,command,cpu,mem,state,time | head -40 ps aux -r | head -30 ``` On Apple Silicon laptops, distinguish real CPU saturation from Spotlight, photo analysis, backup, Docker Desktop, browser tabs, and Xcode indexing before proposing changes. For a remote Linux host, replace `my-server` with the SSH alias: ```bash ssh my-server 'bash -s' < scripts/audit_linux_cpu.sh ssh my-server 'SAMPLES=5 INTERVAL=10 LOG_SCAN=1 bash -s' < scripts/audit_linux_cpu.sh ``` Use `SAMPLES` and `INTERVAL` to collect multiple Docker CPU snapshots. Use