Feat/make alpha more realistic #18
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.
Motivation
The current comparison of the simulated lookups from the ones displayed in probelab.io shows that we are pretty close to simulating accurately a DHT.
Some test already show that the model could be validated with that data:
However, there are a few things that need to be addressed in order to simulate the real behavior of a P2P network:
Related links:
Description
This PR exactly tackles both points, adding a "scheduling" logic to aggregate delays and different rates and delays for "fast" and "slow" errors
Tasks
alpha>1Proof of Success
Tests pass :)