It shines especially in scenarios where the Pi is just a tad too slow. E.g. you can't live transcode 4k videos on a Pi, while the N100 has latest UHD graphics and therefore ships with a decent HW-accelerated H265 en/decoder.
By server i mean multiple network ports and storage ports, space in the case for several spinny discs in addition to the ssds etc.
I doubt any NUC is good for a server by my definition.
The problem is that a lot of the commercial products are woefully underspecc'ed for the price and you outgrow them quickly. Spinning disks also eat a lot of power, relatively speaking, so they kind of eat into the "low power" usecase.
Rather roll my own Linux thank you.
> Some of them even have decent networking options.
I think few of them have multiple ethernet ports. Plus there's the matter of how much cpu the built in ethernet eats.
Most modern NAS have that option. It just doesn’t make that much sense since that would get rid of the (in some cases really good) DSM.
I agree I'd much rather roll my own system (and that's what I did) and I would personally never buy one of those, but it's simply not right to say there are no options available if you want a low power server off the shelf. Some of them are even decent if you wanna pay for it.
https://forums.servethehome.com/index.php?threads/topton-nas...
There is a newer board with a J6413/6412 that could also be a candidate if don’t need quite as much processing power.
Reports are that servers with this run under 10W at idle.
Nothing in this article supports this statement. It just says "high power consumption" without measuring, and declares victory without measuring the power saved. The fact is that power scaling has almost erased the difference between "suspended" and just "idle", to such an extent that there might not even be a meaningful difference, or any measurable difference.
My NUC 12 Pro is drawing, at the wall, 2.7W, as best as I can measure. The SoC reports drawing below 200mW. This server is on. The way to get low power states on these is to just make sure your Linux is up to the task and your BIOS works correctly, which is one of the reasons to choose a NUC. The first-party firmware works!
Another important thing for low-power server operation is to either use wifi, or make sure your ethernet is configured correctly for low-power operation. Unless you fix it, gigabit ethernet by default will propagate the link state all the way down to a high power state on the CPU. The NIC will say that it has tight latency requirements because the link is active, and it will configure the PCIe bus to avoid PCI link power management, and it will tell the CPU that it can't go below PC6. To avoid this you have to configure your NIC to ignore link latency requirements. Just unplugging the ethernet is the easier path, and it's faster than gigabit these days.
Here are some pulling 80W at idle: https://www.anandtech.com/show/17548/the-msi-mpg-z690-carbon...
Here's a threadripper rack server pulling 140W (!!!) at idle: https://www.servethehome.com/asrock-rack-trx40d8-2n2t-review...
You could also use the RPi as a stepping stone which syncs it's files to the 'real' backup server which is on a daily/weekly timer instead of on-demand setup.
I'm using this concept for the problem that I want to collect metrics all day long, but not have a power hungry server running 24/7. So my RPi collects all metrics and streams then directly to my server for me to view realtime. But whenever the server is unavailable (on schedule or for maintenance) the RPi just buffers the metrics until the server is available again.
Also worth considering is just not using a single server for a single purpose but just cramming it full with utility to justify the power costs.