-
Notifications
You must be signed in to change notification settings - Fork 493
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
network: add initial support for latency tracking #3028
network: add initial support for latency tracking #3028
Conversation
Codecov Report
@@ Coverage Diff @@
## master #3028 +/- ##
==========================================
+ Coverage 43.65% 43.67% +0.01%
==========================================
Files 391 391
Lines 86792 86750 -42
==========================================
- Hits 37890 37885 -5
+ Misses 42873 42833 -40
- Partials 6029 6032 +3
Continue to review full report at Codecov.
|
wsPeer already has |
Yes.. this is only a POC. Clearly we won't need to have both when the solution is ready. My goal here was just to do the minimum so that we could measure the connection timing and determine if that aligns with the latencies we're configuring in the Mainnet-model. |
## Summary This PR adds the node ( both client and server ), the ability to measure the time it takes to establish an outgoing connection ( excluding the TCP connection time ). This duration is captured as the initial latency, which would need to get updated via a pingpong style logic. ## Test Plan - [x] Extend existing unit tests - [x] mainnet-model testing is needed as well to confirm correctness
Summary
This PR adds the node ( both client and server ), the ability to measure the time it takes to establish an outgoing connection ( excluding the TCP connection time ).
This duration is captured as the initial latency, which would need to get updated via a pingpong style logic.
Test Plan