[Networking] QUIC transport layer in the libp2p framework · Issue #4280 · onflow/flow-go

The QUIC transport layer is an available component that can be integrated into the libp2p framework, potentially improving network performance. We propose evaluating the QUIC transport layer to determine its suitability for our use case.

Definition of Done

1. The QUIC transport layer has been evaluated for suitability within the libp2p framework.
2. The performance of the QUIC transport layer has been compared against the current transport layer through benchmarking and profiling.
3. The code should be appropriately documented and conform to the Flow coding standards.
4. All tests related to the transport layer should pass.
5. The evaluation should not break any existing functionality or use cases of the libp2p node.
6. QUIC should be added as an alternative transport layer without replacing the current ones. The libp2p nodes should be able to negotiate and agree upon a mutually available transport layer to communicate. The changes should not cause backward compatibility issues.

Testing Results

All the results was made with code located by the link below on the branch 4280-quic-in-libp2p.

https://github.com/AndriiDiachuk/flow-go/tree/AndriiDiachuk/4280-quic-in-libp2p

1. The QUIC transport layer has been evaluated for suitability within the libp2p framework.
2. The performance of the QUIC transport layer has been compared against the current transport layer through benchmarking and profiling.

For running benchmark go to branch above and navigate to flow-go/network/p2p/p2pnode folder and run command: