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

Compute Scheduling #653

Open
mattgeddes opened this issue Nov 9, 2023 · 1 comment
Open

Compute Scheduling #653

mattgeddes opened this issue Nov 9, 2023 · 1 comment
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@mattgeddes
Copy link
Contributor

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:

  1. Contract scheduler -- this would take the compute job request and request it be run on all of the compute nodes in a given quorum.
  2. 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.

@mattgeddes mattgeddes added the enhancement New feature or request label Nov 9, 2023
@mattgeddes mattgeddes added this to the betanet milestone Nov 9, 2023
@vsawant10949
Copy link
Collaborator

What if we extend the Decentralized Task Scheduler for this too? which considers backpressure on compute nodes!

@mattgeddes mattgeddes modified the milestones: betanet, crestone Nov 17, 2023
@mattgeddes mattgeddes modified the milestones: crestone, future Feb 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants