I wouldn't recommend neutrino for a a heavy routing node, it has to make some assumptions about channels since it doesn't have the full chain picture. Neutrino is bet for personal/SMB with a few channels.
A Pi4 likewise is fine for a personal/SMB node, but I wouldn't host a large amount of coin across many channels for routing.
For routing, you really want something with nvme storage at a minimum, ideally redundant storage, and a backup battery to reduce the risk of a corrupted channel state from a failed write.
Performance issues on Pi4's are usually due to inadequate RAM, 4GB is the absolute bare minimum for bitcoind+lnd.
btcd in my experience is a little less memory hungry and is actually an LND library, a better back-end if you're only planning to use it for a Lightning node.
You can also use assumevalid with either bitcoind or btcd up to a recent consensus block to bypass most of the heavy compute at initial sync. Forward blocks will still fully validate/enforce.
The consensus OS for PI's is Armbian afaik, that's just Debian compiled for that hardware and receives all of the same updates. I recommend to enterprise clients not doing auto-updates and instead putting nodes on a militarized network with manual release updates.
Pi's aren't a particularly good value imo since you can get a used laptop with nvme storage, beefier chip, and included battery for less than a few hundred bucks. Never have to fuck with hooking up a KVM is gravy on top.
I wouldn't recommend neutrino for a a heavy routing node, it has to make some assumptions about channels since it doesn't have the full chain picture. Neutrino is bet for personal/SMB with a few channels.
A Pi4 likewise is fine for a personal/SMB node, but I wouldn't host a large amount of coin across many channels for routing.
For routing, you really want something with nvme storage at a minimum, ideally redundant storage, and a backup battery to reduce the risk of a corrupted channel state from a failed write.
Performance issues on Pi4's are usually due to inadequate RAM, 4GB is the absolute bare minimum for bitcoind+lnd.
btcdin my experience is a little less memory hungry and is actually an LND library, a better back-end if you're only planning to use it for a Lightning node.You can also use assumevalid with either bitcoind or btcd up to a recent consensus block to bypass most of the heavy compute at initial sync. Forward blocks will still fully validate/enforce.
The consensus OS for PI's is Armbian afaik, that's just Debian compiled for that hardware and receives all of the same updates. I recommend to enterprise clients not doing auto-updates and instead putting nodes on a militarized network with manual release updates.
Pi's aren't a particularly good value imo since you can get a used laptop with nvme storage, beefier chip, and included battery for less than a few hundred bucks. Never have to fuck with hooking up a KVM is gravy on top.