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

Improve the behavior of receive_pushed #135

Open
rishi-s8 opened this issue Oct 30, 2024 · 0 comments
Open

Improve the behavior of receive_pushed #135

rishi-s8 opened this issue Oct 30, 2024 · 0 comments

Comments

@rishi-s8
Copy link
Collaborator

There are potential caveats with the current version of receive_pushed:

  1. For nodes that lag behind (e.g. in the asynchronous case), the queue size keeps growing, leading to DRAM OOM.
  2. When a node calls receive_pushed, the first model per neighbor is taken which might be old. The first model should be used in the synchronous case, whereas only the latest model should be used in the asynchronous case.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant