link speed estimates #3
Merged
Conversation
This file contains 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
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.
Implement an algorithm for link speed estimates.
In terms of architecture the algorithm can even be used as a streaming algorithm.
The actuall calculations of the quality score and velocities are conceptually similar to the BMW proposal, but avoid the problems I mentioned in my email.
So far no upper and lower bounds are derived, so thats a TODO, but I'd like to talk through the semantics of that beforehand.
Another TODO is taking speed limits on links into account.
Nevertheless, this seems like a very good start to me.
The estimator state machine feels like a very well fitting and extensible way to decompose the complexity of the problem.