cpu-gpu-performance

## Table of Contents - [When to Use](#when-to-use) - [Required TodoWrite Items](#required-todowrite-items) - [Step 1: Establish Current Baseline](#step-1-establish-current-baseline) - [Step 2: Narrow the Scope](#step-2-narrow-the-scope) - [Step 3: Instrument Before You Optimize](#step-3-instrument-before-you-optimize) - [Step 4: Throttle and Sequence Work](#step-4-throttle-and-sequence-work) - [Step 5: Log Decisions and Next Steps](#step-5-log-decisions-and-next-steps) - [Output Expectations](#output-expectations) # CPU/GPU Performance Discipline ## When To Use - At the beginning of every session (auto-load alongside `token-conservation`). - Whenever you plan to build, train, or test anything that could pin CPU cores or GPUs for more than a minute. - Before retrying a failing command that previously consumed significant resources. ## When NOT To Use - Simple operations with no resource impact - Quick single-file operations ## Required TodoWrite Items 1. `cpu-gpu-performance:baseline` 2. `cpu-gpu-performance:scope` 3. `cpu-gpu-performance:instrument` 4. `cpu-gpu-performance:throttle` 5. `cpu-gpu-performance:log` ## Step 1: Establish Current Baseline - Capture current utilization: - `uptime` - `ps -eo pcpu,cmd | head` - `nvidia-smi --query-gpu=utilization.gpu,memory.used --format=csv` Note which hosts/GPUs are already busy. - Record any CI/cluster budgets (time quotas, GPU hours) before launching work. - Set a per-task CPU minute / GPU minute budget that resp...