Skip to content

Improve the behavior of receive_pushed #135

Description

@rishi-s8

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions