As far as I remember, I deleted any blockexplorer containers, the Electrum server container, basically all stuff that could possibly eat up significant performance. I set dbcache=5120 in Umbrel and started the IBD, no old blockchain data was left from the previous deletion of the Bitcoin Core container in Umbrel (I checked).
My internet connection has stable 110MBit/s downstream and ~40MBit/s upstream; Umbrel connects via Tor and I2P only; storage media was a Samsung 860 SATA SSD connected with an USB3-SATA-interface supporting proper UASP protocol. Other notable config options were (not all are listed here):
Code:
dbcache=4883 # though I passed 5120 in Umbrel settings... interesting how Umbrel disobeys this!
onlynet="onion"
onlynet="i2p"
txindex=1
blockfilterindex=1
peerblockfilters=1
peerbloomfilters=1
IBD ran uninterrupted from 2023-06-22T18:00Z until 2023-06-26T16:46Z when it reached progress=1.000000 at blockheight 796033. That's little less than 95h, not bad for a Raspi 4B. During IBD I didn't login to the Umbrel webinterface, only checked progress once or twice a day via SSH login and peeking into Core's debug.log file.
My question to OP: what's your goal, as fast as possible IBD or what else? How is your storage attached to your Pi5?
With a Pi5 (I still don't have one, waiting for the CM5 module with 16GB RAM that was announced recently) I would use a M.2 NVMe SSD adapter board which gives way faster mass storage transfer rates than a Pi4 could ever dream of.
You didn't say anything regarding your Pi5's mass storage. Consider also option blocksonly=1 during IBD, so your node doesn't have to bother with mempool and transaction verification.
