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

Create formal split between runtime and backend in workflow interface #676

Open
psfoley opened this issue Jan 10, 2023 · 0 comments
Open
Milestone

Comments

@psfoley
Copy link
Contributor

psfoley commented Jan 10, 2023

In the initial release of the workflow interface, the LocalRuntime has two backends that can be used that define how the experiment is executed on a single node: The default option is to launch all tasks within a single process, or parallel execution with the Ray library (by setting LocalRuntime(..., backend='ray'). While only two backends are defined for the LocalRuntime today, there should be clean separation between these for future expandability.

This task involves creating and documenting a Backend interface, and refactoring the LocalRuntime (and any additional Runtime implementations) from the backend (i.e. a LocalSingleProcessBackend or LocalRayBackend ). This will lead to cleaner maintainance of code, and help external contributors design new backends for the project.

@psfoley psfoley added this to the v1.6 milestone Jan 10, 2023
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