Skip to content
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.

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

Network congestion and deadlock #42

Open
lplana opened this issue May 6, 2021 · 0 comments
Open

Network congestion and deadlock #42

lplana opened this issue May 6, 2021 · 0 comments
Assignees
Labels

Comments

@lplana
Copy link
Member

lplana commented May 6, 2021

Network congestion is present in large networks and congestion leads to packet dropping.

  • dropped packets are not necessarily a correctness issue as they are reinjected and correctly processed.
  • dropped packets are a performance issue, as dropped packets are delayed, in turn delaying computation.

Occasionally, dropped packets can not be picked up by the reinjector and are permanently lost. leading to deadlock as every packet is required to complete the computation.

  • permanently lost packets are a correctness issue.

The current implementation does not have a way of dealing with permanently lost packets.

@lplana lplana added the bug label May 6, 2021
@lplana lplana self-assigned this May 6, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant