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

Start implementing concurrency #11

Closed
fabiodrg opened this issue Apr 6, 2019 · 2 comments
Closed

Start implementing concurrency #11

fabiodrg opened this issue Apr 6, 2019 · 2 comments
Assignees
Labels
Critical Priority

Comments

@fabiodrg
Copy link
Collaborator

fabiodrg commented Apr 6, 2019

No description provided.

@fabiodrg fabiodrg added the Critical Priority label Apr 6, 2019
@fabiodrg
Copy link
Collaborator Author

fabiodrg commented Apr 7, 2019

Each peer has three multicast channels. Maybe three threads could be launched per peer. Each thread should be responsible for listening to one of the channels and dispatch the datagram packets received to new workers. Each worker (a new thread) should process the message and perform the desired action.

However, from my understanding, we should limit the number of threads being launched due to huge increments in latency. This probably is something we want to test and study later on to find a good value. Considering this limitation, then we need to have some sort of FIFO to store the incoming datagrams.

Does it make sense @Dannyps ?

@Dannyps
Copy link
Owner

Dannyps commented Apr 8, 2019

we should limit the number of threads being launched due to huge increments in latency

Where does this come from? I can't see the issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Critical Priority
Projects
None yet
Development

No branches or pull requests

2 participants