---
name: agenthub-server-box-hardware
description: "This dev box becomes the team AgentHub server — 4-core/15 GB, SSD+HDD; lag was the HDD, not AgentHub; measured server capacity"
metadata:
  node_type: memory
  type: project
  originSessionId: 3e920c96-dcc6-48df-945b-419d9705015b
  modified: 2026-10-08T07:04:34.801Z
---

Box (measured 2026-10-08): Intel 100-series (Skylake) 4 cores, 15 GB RAM, SSD `sdb` 224 GB (/), HDD `sda` 500 GB with bind mounts for `~/.nvm`, `~/.local`, `~/.config` (Chrome profile), `~/.cache`, Docker, /var/log, /mnt/hdd. That HDD sat at 93–96 % util, 15–24 % iowait — the cause of the user's "lag", not AgentHub.

AgentHub measured: 4820 p99 4.8 ms with 3 sessions; peak real load 7–11 hooks/s; isolated copy of the 1.25 GB DB handled 100 hooks/s + 10 viewers at p99 ~40 ms, saturates ~200 hooks/s + 20 viewers (one Node thread, viewer refetches dominate). Real multi-user limit is RAM (~400 MB per `claude` process).

User plan: reinstall the OS, everything on SSD, HDD only for backups (/mnt/hdd), keep the GUI (they watch the box), move personal data to their Mac first; 4830 dev runs here until then, then only 4820. Daily DB backup to the HDD = Settings → Data → Daily backup (server/lib/db-backup.js, built 10-08, uncommitted on main).

**Why:** the user asked about a Rust/TS rewrite for speed; the numbers say no.

**How to apply:** answer perf/scaling questions from these numbers; suggest RAM (32 GB) before any rewrite; don't recreate HDD bind mounts for hot dirs. See [[agenthub-multi-user-goal]].