I am running a custom implementation of the topology updater using the pi.clio.one/htopology web service, but I can’t find any setting to limit the number of peers my IP is propagated to.
I was thinking more of a setting for the cardano-node to gracefully reject connections when a certain upper limit is reached,
Nevertheless, I have been monitoring my relays for the past few weeks and in spite of having up to 40 inbound connections causing outbound traffic spikes of 850Kb/s, the performances are acceptable and the nodes are working fine.
Something that helped my nodes coping better with all those inbound traffic was to:
- disable TraceMempool in the config.json for the relays only (Error: Switchboard's queue full, dropping log items!)
- enable a 4G swap file for the relays only (Why my relay node crashes and restarts at the end of each epoch?)
- systematically restart my relay nodes every 8 days
I hope this help!