The volume and size of peer-to-peer communication for a Zilliqa node is controlled by several factors at different parts of the stack.
MIN_READ_WATERMARK_IN_BYTES: The minimum number of bytes read from the socket before we act on the data. It is basically the
lowmarkparameter required by the libevent function
MAX_READ_WATERMARK_IN_BYTES: The maximum number of bytes read from the socket before we stop accepting further input. It is basically the
highmarkparameter required by the libevent function
MAX_GOSSIP_MSG_SIZE_IN_BYTES: The maximum size of a socket message with start byte =
START_BYTE_GOSSIP. If a message reaches this size, the sender is blacklisted.
MAXSENDMESSAGE: The number of active threads for the outgoing message pool.
MAXRECVMESSAGE: The number of active threads for the incoming message pool.
SENDQUEUE_SIZE: The maximum size of the outgoing message queue (before transfer to the outgoing pool), beyond which any further messages are dropped.
MSGQUEUE_SIZE: The maximum size of the incoming message queue (before transfer to the incoming pool), beyond which any further messages are dropped.
MAXRETRYCONN: The maximum number of socket connection attempts to perform for sending messages to a peer.
PUMPMESSAGE_MILLISECONDS: The maximum wait time (minimum being 1 ms) before re-attempting socket connection.
MAX_PEER_CONNECTION: The maximum number of active connections to a specific peer.