Comm layer performance #797
Description
Currently the main implementation used for communication is based on web sockets. Previously we used libp2p but we transitioned in order to support custom routing (necessary for node replication), and multi-node tracing (transfer context between nodes is not supported for libp2p out of the box).
However, the most important criterion would be the actual performance of the communication layer. The applications currently support both modes (all integration tests test against both ways), but if we want to decommission libp2p, we will need to have some performance tests to test that web sockets don't have a negative impact on performance.