Even with the powersave governor pushing them down to 800Mhz they stay snappy, and rarely go above 1.2GHz, except when I compile stuff, or do logic-simulations. But I have other, more modern stuff for that. OTOH with things like distcc/Icecream they can be useful helpers.
Edit: Suspend to RAM/wakeup (via whichever mechanism(even via keycombo or special key on modern Keyboard)), WOL, NetBoot/PXE works every single time.
4K video? No problem.
Hackintosh? Check. But why? There's QEMU. (Am not a Mac person anyways)
Genode? Check. Much more interesting running native/bare metal.
The quality of the BIOS/UEFI is phenomenal, like Thinkpad legendary.
I do totally get it for building wiring, where the patch panel is used to bulk terminate cables going elsewhere into fixed 2-post racks, and the patch cords take care of the higher level concern of assigning switch ports. But doing it on a home server rack just feels like cargo cult copying that pattern for not much gain.
I did this before the pandemic for a "real" K8s environment (history is 20/20, but this rocked for what I needed then).
Basically a super inexpensive and tiny i7-4600U laptops w/o display that I upgraded to 16GB of RAM and 256 SSDs. I still run a smaller fleet for different services and testing - both standalone and as part of a Proxmox cluster.
I donated to Mr. Chromebox for years, super awesome work.
p_ing•8mo ago
(Progress Quest is awesome)
LargoLasskhyfv•8mo ago
OFC they are 'better', and have much more oomph.
p_ing•8mo ago
LargoLasskhyfv•8mo ago
'Home-lab' can mean many different things. When you put some common OS on a thing, and then run that head-less 24/7 to fiddle with virtualization/containerization/clustering on top of that OS mostly, the 'quality' of the BIOS/UEFI doesn't really matter.
It's used during initial setup, and that's it. Maybe some tuning, but one interacts not that often with it.
This changes when one uses that thing to throw anything at it that was ever made for AMD64. Exotic stuff like Genode, for instance. Though that also is a question of hardware and driver support.
This continues with the implementation of ACPI, leading to the cleanest bootlogs ever, with no errors at all. It goes on with all sorts of Netbooting/PXE, be it as a client, or server. Other niceties are suspend to ram, wake on lan, reliably working every single time.
This is amplified by having several of them, using at least some of them not 24/7 with the same setup, but changing everything, suspending them, or shutting them down, using them only on demand (via WOL/magic packet), testing failover/HA, and whatnot else.
Again, without interacting with the BIOS/UEFI, it just has to work with everything behind the scenes.
That's what I meant to say in the context of home-lab. It needs to be able to flawlessly work with all sorts of ever changing stuff.
Which is not a given.