Node connection to other Nodes exp. High latency - Stale connections - Lack of connection pruning

[surfercool]

In the Futurebit Apollo 2 Node, there are usually a large number of connected nodes with ping times well over 200ms. This makes it nearly impossible to send a found block to the network in a timely manner.

High latency:
The nodes connected to the Apollo 2 Node are experiencing very high latency (ping times), which is significantly impacting the ability to broadcast new blocks to the network in a timely manner.

Stale connections:
A large number of connections are being kept open, even though the nodes on the other end are no longer responding. This is consuming unnecessary resources and potentially hindering network performance.

Lack of connection pruning:
There is no mechanism in place to automatically disconnect nodes that are not responding within a reasonable timeframe.

A potential solution:
Implement a ping-based connection pruning mechanism: The node should periodically send ping requests to all connected nodes. If a node fails to respond within a specified timeout (e.g., 30ms), the connection should be terminated. This will help to ensure that only healthy and responsive nodes remain connected.