Nikola Mitev on Nostr: For anyone who decides to run their own node, some notes from my personal experience ...
For anyone who decides to run their own node, some notes from my personal experience with this:\
1) initial synchronisation took weeks, until I gave the host 16GB ram and changed the setup from 1 HDD to 2 HDDs in a LVM volume. The RAM increase together with increased disk throughput made a big difference. Would have been even better to be able to use SSD and/or striped RAID.\
2) once synchronised, much less RAM is needed - right now my node is using less than 2GB\
3) the host is currently using just under 700GB disk space, so have at the very least 1TB for your node.\
4) any CPU should be fine\
5) after applying some limits in the config file, I get on average 1.2Mb/s upload and 30Kb/s download network utilisation\
\
Config file options to consider on top of what is in the guides:\
# limit network utilisation - I used 84G as the value, didn't do much testing\
maxuploadtarget=84G
\# allow peerbloomfilters so Bisq can use the node\
peerbloomfilters=1
\# whitelist some hosts which you want to be able to use the node\
whitelist=bloomfilter,download,noban,mempool,relay@192.168.1.1\
whitelist=bloomfilter,download,noban,mempool,relay@192.168.1.2
\# allow JSON-RPC from those hosts too. It may be possible to tighten permissions but for me limiting the access to a few trusted hosts is good enough. Remember to keep localhost in there so you can run cli commands from the host.\
rpcallowip=127.0.0.1
rpcallowip=192.168.1.1\
rpcallowip=192.168.1.2
\# listen on the public IP and localhost\
rpcbind=192.168.1.100\
rpcbind=127.0.0.1
\# configure the username and password for the rpc account\
# sparrow and local cli commands need this, bisq does not\
rpcpassword=yourpass\
rpcuser=youruser
\
For me personally, the biggest benefit is faster sync times for wallets and Bisq when connecting to my own node instead of public ones.
1) initial synchronisation took weeks, until I gave the host 16GB ram and changed the setup from 1 HDD to 2 HDDs in a LVM volume. The RAM increase together with increased disk throughput made a big difference. Would have been even better to be able to use SSD and/or striped RAID.\
2) once synchronised, much less RAM is needed - right now my node is using less than 2GB\
3) the host is currently using just under 700GB disk space, so have at the very least 1TB for your node.\
4) any CPU should be fine\
5) after applying some limits in the config file, I get on average 1.2Mb/s upload and 30Kb/s download network utilisation\
\
Config file options to consider on top of what is in the guides:\
# limit network utilisation - I used 84G as the value, didn't do much testing\
maxuploadtarget=84G
\# allow peerbloomfilters so Bisq can use the node\
peerbloomfilters=1
\# whitelist some hosts which you want to be able to use the node\
whitelist=bloomfilter,download,noban,mempool,relay@192.168.1.1\
whitelist=bloomfilter,download,noban,mempool,relay@192.168.1.2
\# allow JSON-RPC from those hosts too. It may be possible to tighten permissions but for me limiting the access to a few trusted hosts is good enough. Remember to keep localhost in there so you can run cli commands from the host.\
rpcallowip=127.0.0.1
rpcallowip=192.168.1.1\
rpcallowip=192.168.1.2
\# listen on the public IP and localhost\
rpcbind=192.168.1.100\
rpcbind=127.0.0.1
\# configure the username and password for the rpc account\
# sparrow and local cli commands need this, bisq does not\
rpcpassword=yourpass\
rpcuser=youruser
\
For me personally, the biggest benefit is faster sync times for wallets and Bisq when connecting to my own node instead of public ones.