Another latency experiment #299
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The previous latency calculations are still being evaluated, but I would like to also test latency latency calculations based on lat/long coordinates. In this experimenal code we'll get the lat/long from cloudflare and use that to estimate the latency between peers. We can then evaluate this value next to the previous latency value based on base station pings, and the latency we measure between peers. We'll also store the lat/long coordinates with the `avg-latency-at-10s` event. This way we can start building a map of latencies between coordinates in the world. We could use this map to more accurately predict latencies in the future.
koenbollen
approved these changes
Dec 2, 2025
Collaborator
koenbollen
left a comment
koenbollen
left a comment
There was a problem hiding this comment.
looks good for an experiment.
Pedr0Rocha
approved these changes
Dec 3, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The previous latency calculations are still being evaluated, but I would like to also test latency latency calculations based on lat/long coordinates.
In this experimenal code we'll get the lat/long from cloudflare and use that to estimate the latency between peers.
We can then evaluate this value next to the previous latency value based on base station pings, and the latency we measure between peers.
We'll also store the lat/long coordinates with the
avg-latency-at-10sevent. This way we can start building a map of latencies between coordinates in the world. We could use this map to more accurately predict latencies in the future.