My lab: the hardware behind the posts
The machines behind every field test on this blog, so later posts can just link here.
Why a homelab
I’d rather test a claim than just repeat it. Papers and vendors report results on their own hardware, under conditions I can’t see and sometimes can’t reproduce. Running the same code on my own machines gives me numbers I can stand behind, shows what changes when the hardware does, and helps me find use cases in the details.
It’s also cheap enough to stay curious. A run at home costs electricity, not an hourly bill, so I can repeat it until I trust it. Plus, it is fun!
I’ve collected many components over the years; these are the ones I keep using.
The machines
| Machine | Role |
|---|---|
| Raspberry Pis, several generations | Edge and constrained-resource experiments |
| Intel NUCs (i3, i5 and i7), running Proxmox | Clustering, distributed systems, CPU inference, the monitoring stack |
| GMKtec EVO-X2, 128 GB unified memory | Large models on AMD hardware |
| Google Cloud GPUs and TPUs | Special cases, such as checking a result on datacenter hardware; used briefly, with hard cost limits |
The details
Each field test describes its exact setup and method in its “Under the hood” section, and its code and results are public in under-the-hood.