Parameters for heavy duty full node | Bitcointalksearch.org

unamis76

legendary

Activity: 1512

Merit: 1012

Quote from: rico666 on February 23, 2016, 10:52:10 AM

Quote from: unamis76 on February 23, 2016, 10:39:31 AM

A "heavy duty" node is a node with lots of RAM and nice bandwidth... There's not much else to it

A fast SSD and a nice processor also help.

Thanks, but obviously my node with its 8 CPUs, 64GB RAM, 2.2GB/s IO and dedicated 1Gps right on the ISP switch is nowhere near utilizing the hardware with the default parameters. That's why I am asking how to tweak these to make use of the hardware (and be useful to the network).

Rico

If that's so, then maybe we found an overkill node

How much RAM is bitcoind using?

shorena

copper member

Activity: 1498

Merit: 1528

No I dont escrow anymore.

Quote from: rico666 on February 23, 2016, 11:48:50 AM

# uptime
17:47:49 up 35 days, 19:42, 1 user, load average: 0.14, 0.21, 0.29

# bitcoin-cli getconnectioncount
97

Sounds good to me as you are pretty close to the default max (125). From personal experience the NI value will mostly improve over time. The longer your node runs the more connections to other nodes than are constantly online. This should in turn improve their reachability, because they tend to have open ports.

rico666

legendary

Activity: 1120

Merit: 1037

฿ → ∞

# uptime
17:47:49 up 35 days, 19:42, 1 user, load average: 0.14, 0.21, 0.29

# bitcoin-cli getconnectioncount
97

shorena

copper member

Activity: 1498

Merit: 1528

No I dont escrow anymore.

Quote from: rico666 on February 23, 2016, 10:52:10 AM

Quote from: unamis76 on February 23, 2016, 10:39:31 AM

A "heavy duty" node is a node with lots of RAM and nice bandwidth... There's not much else to it

A fast SSD and a nice processor also help.

Thanks, but obviously my node with its 8 CPUs, 64GB RAM, 2.2GB/s IO and dedicated 1Gps right on the ISP switch is nowhere near utilizing the hardware with the default parameters. That's why I am asking how to tweak these to make use of the hardware (and be useful to the network).

Rico

How long has it been online and how many connections does it currently have?

rico666

legendary

Activity: 1120

Merit: 1037

฿ → ∞

Quote from: unamis76 on February 23, 2016, 10:39:31 AM

A "heavy duty" node is a node with lots of RAM and nice bandwidth... There's not much else to it

A fast SSD and a nice processor also help.

Thanks, but obviously my node with its 8 CPUs, 64GB RAM, 2.2GB/s IO and dedicated 1Gps right on the ISP switch is nowhere near utilizing the hardware with the default parameters. That's why I am asking how to tweak these to make use of the hardware (and be useful to the network).

Rico

unamis76

legendary

Activity: 1512

Merit: 1012

A "heavy duty" node is a node with lots of RAM and nice bandwidth... There's not much else to it

A fast SSD and a nice processor also help.

rico666

legendary

Activity: 1120

Merit: 1037

฿ → ∞

Hi,

I've been running a full node for quite some time and am pretty high in the https://bitnodes.21.co/nodes/leaderboard/ - it's fun.

However - in the metrics of the leaderboard computation, there is a

NI = Nodes index
NI = (p ∩ N) / N
p = number of peers returned in addr responses
N = number of reachable nodes

which is constantly low with my node and it seems no one gets really high numbers there.
What parameters would I need to feed to bitcoind, so that number gets higher?
Also this brings me to the more generic question "What parameters could I use to run a really really heavy duty full node?"
By heavy duty I mean a full node "serving" a lot of peers.
The machine I run it on could probably pull a lot, so I would like to test the limits.

Thanks for the hints.

Rico

Topic: Parameters for heavy duty full node (Read 591 times)