You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
Why:
Related to:
#1376
The text was updated successfully, but these errors were encountered: