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

measure the health of hypercores #3

Open
2 tasks
Tracked by #1
serapath opened this issue Jan 15, 2020 · 0 comments
Open
2 tasks
Tracked by #1

measure the health of hypercores #3

serapath opened this issue Jan 15, 2020 · 0 comments

Comments

@serapath
Copy link
Member

serapath commented Jan 15, 2020

@todo

  • make a command line tool to receive a "dat address" as an argument and return "the health" either as a one time snapshot or allow to subscribe to continuously receive updates.
    • "dat address" (can be for hypercores, hyperdrives, hypertries, etc...)
    • the meaning of "the health" depends on what you think we can get:
      • e.g. how many hypercores are involved (e.g. hyperdrives have 2)?
      • e.g. how many peers participate in the swarm?
      • e.g. what is the throughput (download) possible?
      • e.g. how often is each chunk duplicated?
      • e.g. what is the fluctuation of peers?
      • e.g. what is the latency for particular chunks?
      • e.g. etc...
  • additionally it would be cool to support also kappa-* stuff if that's possible :-)
    • if i'm not mistaken kappa still uses hypercores underneath it all

Of course we wan't it modular, so we can re-use individually the logic to figure out from a "dat address" whether we are dealing with a hypercore, a hyperdrive, a hypertrie or something else.
We want to be able to listen to the module to keep on receiving data about the health and we might want to store the history, so when we ask the command line tool for the same address, it already has some historical data.

Any feedback or suggestion for how to approach this or do it maybe even differently are welcome :-)

@serapath serapath mentioned this issue Jan 15, 2020
12 tasks
@ninabreznik ninabreznik changed the title measure the health of a dat address measure the health of hypercore Jan 15, 2020
@ninabreznik ninabreznik changed the title measure the health of hypercore measure the health of hypercores Jan 15, 2020
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