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
This was another issue that came out of Friday's call that I said I'd raise and am just getting to now.
When an RPC call comes in from the outside world to request the execution of a compute job, the Protocol needs to be able to schedule that job across the network to varying extents and depending on the type of job that it is. We anticipate seeing a variety of approaches to scheduling jobs in the future, but for betanet, we only need to see two implemented:
Contract scheduler -- this would take the compute job request and request it be run on all of the compute nodes in a given quorum.
Ad-hoc scheduler -- this is a very simple scheduler that just has the job execute on any one node in the network or a given quorum (I believe that in betanet network == quorum anyway). This is for the prototype non-contract compute case.
Feel free to break this down into smaller chunks or add any extra detail here.
The text was updated successfully, but these errors were encountered:
This was another issue that came out of Friday's call that I said I'd raise and am just getting to now.
When an RPC call comes in from the outside world to request the execution of a compute job, the Protocol needs to be able to schedule that job across the network to varying extents and depending on the type of job that it is. We anticipate seeing a variety of approaches to scheduling jobs in the future, but for betanet, we only need to see two implemented:
network == quorum
anyway). This is for the prototype non-contract compute case.Feel free to break this down into smaller chunks or add any extra detail here.
The text was updated successfully, but these errors were encountered: