New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

QUIC network implementation #4

Closed

nikkolasg opened this issue Nov 27, 2018 · 1 comment

Assignees

Collaborator

nikkolasg commented Nov 27, 2018

Add a QUIC network implementation to Handel.

bkolad self-assigned this

bkolad closed this as completed

Contributor

bkolad commented Mar 11, 2019 •

edited

Loading

The QUIC network is around 4 times slower than the UDP network.
The performance hit can be explained by 2 reasons

handshake phase (which we don't have for UDP based network)
and QUIC-go doesn't support 0-RTT handshake yet:
implement 0-RTT handshakes quic-go/quic-go#438 (reference)
the T2 nano aws instances are one core machines (and we are already using it for signature verification). According to this presentation QUIC can be 2x more CPU demanding than TCP.
https://www.youtube.com/watch?v=B1SQFjIXJtc#t=25m53s
Also QUIC is encrypted by default.

Update:
After playing with the AcceptCookie callback I managed to decrease the performance hit to 3x of UDP network for 500 nodes.

UDP: 0.4094
QUIC: 1.237

bkolad mentioned this issue

Use QUIC for all communications between peers ethresearch/p2p#8

Open

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment