benchmark

name

benchmark

description

Run a system benchmark tailored to the detected hardware on a Linux desktop. CPU (sysbench / stress-ng), GPU (glmark2 / vkmark / clpeak — chosen by GPU vendor), disk I/O (fio against the benchmark folder's filesystem), memory (sysbench memory + mbw), and a quick desktop-responsiveness probe. Saves timestamped JSON + Markdown summary to the user-defined benchmark folder. Triggers on "benchmark my system", "run benchmark", "rebench", or as a follow-up to `onboard`.

Benchmark

Single-shot benchmark run. Reads the detected system_profile from config, selects appropriate tools, runs them with conservative durations (default 30s per CPU/memory test, 1-minute fio job), then writes results.

Config

${CLAUDE_USER_DATA:-${XDG_DATA_HOME:-$HOME/.local/share}/claude-plugins}/linux-system-optimisation/config.json

If missing → call onboard first. The benchmarks_dir field tells you where to save results.

Output layout

Inside benchmarks_dir:

<ISO-timestamp>/
├── results.json      # machine-readable
├── summary.md        # human-readable, ranked findings + suggested next steps
└── raw/              # raw stdout from each tool

Suite

Pick per detected hardware. Skip a group with a clear reason if a tool isn't applicable.

• CPU
  • sysbench cpu --threads=$(nproc) --time=30 run — events/sec.
  • stress-ng --cpu $(nproc) --cpu-method=matrixprod --metrics-brief --timeout 30s — bogo-ops.
  • Capture pre/post cat /proc/cpuinfo | grep MHz and sensors to see thermal/throttle behaviour.
• GPU (vendor-aware)
  • NVIDIA: glmark2, vkmark, nvidia-smi --query-gpu=power.draw,temperature.gpu,clocks.gr --format=csv -l 1 during run.
  • AMD: glmark2, vkmark, radeontop -d- (sample) during run.
  • Intel: glmark2, intel_gpu_top -J (sample) during run.
• Memory
  • sysbench memory --memory-block-size=1M --memory-total-size=10G run
  • mbw -q 1024 (1 GB block, MB/s)
• Disk I/O — run against benchmarks_dir's filesystem (so the test is on the same disk class the user actually uses).
  • fio --name=randread --rw=randread --bs=4k --size=1G --runtime=60 --time_based --ioengine=libaio --direct=1 --output-format=json
  • Same with --rw=randwrite. Clean up the test file after.
• Desktop responsiveness (rough)
  • Capture vmstat 1 5 and pidstat 1 5 while running a brief CPU+memory mixed load (stress-ng --cpu 2 --vm 2 --vm-bytes 1G --timeout 5s).

Result schema (results.json)

{
  "timestamp": "<ISO-8601>",
  "host": { "kernel": "...", "distro": "...", "de": "...", "session": "..." },
  "cpu": { "sysbench_events_per_sec": 0, "stress_ng_bogo_ops": 0, "max_freq_mhz": 0, "throttled": false },
  "gpu": { "vendor": "...", "glmark2_score": 0, "vkmark_score": 0     
        
            
        

Summary.md

Brief, scannable. Lead with anything red-flagged: thermal throttling under CPU load, GPU power-cap hits, disk IOPS far below class expectations, swap thrash. Each finding pairs with a suggested action that optimise can act on.