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

DataTask Locality Considerations #29

Open
Keith-Bateman opened this issue Apr 23, 2024 · 0 comments
Open

DataTask Locality Considerations #29

Keith-Bateman opened this issue Apr 23, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@Keith-Bateman
Copy link
Member

Is your feature request related to a problem? Please describe.
When executing a DataTask, it might be better to create multiple copies of data in order to improve locality of future accesses. This could also be performed during composition or scheduling, and it isn't immediately clear where the best place to replicate DataTasks is.

Describe the solution you'd like
Explore replication policies that can give improved locality, likely using an AI predictor to decide which data will be likely to be accessed in the future.

@Keith-Bateman Keith-Bateman added the enhancement New feature or request label Apr 23, 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

1 participant