Commit Graph

3 Commits

Author SHA1 Message Date
m3ultra
4c05a9daa8 docs: wan_video + ardy_motion measured RAM/speed (two-machine verification)
wan_video 5B q8 verified clean on M3 Ultra (148.7s) and M2 Max (503.7s),
identical 9.2GB max RSS on both; 81GB 'footprint' on m2max identified as
MLX opportunistic cache, not demand. Frame-identical output at same seed
across machines. HARDWARE.md gains wan_video and ardy_motion rows.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-08-05 16:44:08 +10:00
type-two
b9de2a4167 docs: register the M1 Max / M4 mini / M1 mini nodes in CLUSTER + HARDWARE
These three were onboarded on 2026-07-17 and are live in nodes.json, but the docs
still described a three-machine fleet (M3 Ultra / M1 Ultra / M4 Pro). Anyone reading
CLUSTER.md to decide where a job should land was working from a stale map.

Records the M1 Max as a second full gen node (flux_local, hunyuan3d_mlx; NOT trellis
- M1 bf16), and the M4 mini / M1 mini as light bg_remove + cpu helpers. Also notes
the M1 Max login split: admin is `m1max`, but the checkout and farm run as `studio`,
which needs /opt/homebrew/bin on its login PATH.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-07-17 22:24:36 +10:00
m3ultra
876a666e9a HARDWARE.md: per-operator RAM + Apple Silicon tier guide (8GB→256GB) 2026-07-16 14:00:39 +10:00