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

[k2] SPIKE: Peer Behavior Module #42

Open
neonphog opened this issue Dec 3, 2024 · 0 comments
Open

[k2] SPIKE: Peer Behavior Module #42

neonphog opened this issue Dec 3, 2024 · 0 comments

Comments

@neonphog
Copy link
Collaborator

neonphog commented Dec 3, 2024

We need a way to understand cross-module some information about peer interactions:

  • We want to know if a peer has recently been unresponsive, so we can skip even trying to communicate with them for a time period
  • We want to know if we've sent too much data to a specific peer lately, so we want to slow down comms to not use all their bandwith
  • We want to know if we've received too much data from a specific peer so we can close the connection with them to avoid all our bandwidth being used

We don't want this to be a "metrics" module.

A "Behavior" module to facilitate this type of information gathering should be designed.

  • what all do we want to include in this module for the first iteration
  • do these things need to be persisted, or should they be runtime memory only

This spike may produce a working module : )

Time Box: 3 Days

@github-project-automation github-project-automation bot moved this to Backlog in Holochain Dec 3, 2024
@neonphog neonphog moved this from Backlog to Ready for refinement in Holochain Dec 4, 2024
@neonphog neonphog assigned neonphog and unassigned neonphog Dec 4, 2024
@neonphog neonphog moved this from Ready for refinement to Ready in Holochain Dec 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Ready
Development

No branches or pull requests

1 participant