Hey,

I think monero is interesting and want to support it a little. To do so i setup a public full node on my home-server (3900x with NVMe SSD) and configured it so that it is allowed to use up to 50% of my bandwidth (i have 500 MBit/s down and 40 MBit/s up)

I’m now not that sure how to configure in-peers and out-peers in a way that strengthens the network. My assumption would be that a high number of out-peers is bad because my server would be blocking in-connections of other nodes, and a high number if in-peers is good because i allow more people to download the chain.

Are these assumptions correct?
What would be some good values for in-peers and out-peers?
I currently configured 128 out-peers and 1024 in-peers. Is one of these exessive or not enough?

Update: I decided to go with 64 out-peers and 256 in-peers for now. See this comment for an explanation

  • shortwavesurfer
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    Well, it sounds like you would only be able to serve 20mbps worth of in peers whatever that number may be. I think mine is set to 8 out and 16 in but i only have 50mbps/10mbps

      • shortwavesurfer
        link
        fedilink
        English
        arrow-up
        1
        ·
        edit-2
        1 year ago

        Since you brought it up, I’ve been experimenting. What you can do is set --limit-rate-up. I set mine to 1024 (1MB/s (8.1mbps)) the default is 2048 (2MB/S (16.2mbps.)). I upped my numbers to 64(out)+64(in) and i am finding on average its using ~12% of the 1MB/s (8.1mbps) i have it limited to. Mind you, most peers already have the chain so mostly its going to be relaying new blocks. But that is why i set the --limit-rate-up so my network isnt murdered if a peer needs the whole chain.

        Edit: Also, it took me quite a while to establish 64 inbound connections over an hour anyway. The 64 outbound connections were established within seconds, but it takes a while to get the incoming peers.