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

Transfers/Deployment progress reporting for Requestor #1399

Open
nieznanysprawiciel opened this issue Jun 9, 2021 · 1 comment
Open

Transfers/Deployment progress reporting for Requestor #1399

nieznanysprawiciel opened this issue Jun 9, 2021 · 1 comment

Comments

@nieznanysprawiciel
Copy link
Contributor

Why:

  • Requestor doesn't know if Provider stopped working or downloading image lasts so long

Related to:
#1376

@mfranciszkiewicz
Copy link
Contributor

mfranciszkiewicz commented Jun 9, 2021

Requestors may query activity state / running command at any time via GSB; it's easy to tell whether the activity is alive and what command is running. Also, instead of reporting (push), transfer progress (+ e.g. speed, eta, start time) could be stored as activity state metadata. State metadata will most probably be implemented because of services.

I see the following benefits that transfer progress reporting may bring:

  • underperforming providers could be killed off earlier
  • computation deadline can be extended while downloading results
  • state reports in requestor's logs
  • better (manual) computation time predictions

If we want to extend the deadline because while deploying, the only situation I see it in as beneficial is when there is a long-term starvation of providers or there are few providers with rare hardware resources. Otherwise, we'd decide for the requestor to spend more on nodes that:

  • didn't start computing because they were downloading the image
  • there is no guarantee that they will further participate in computation
  • should be banned or have their reputation decreased

when there are providers that will perform the computation much faster

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

2 participants