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

[ray] Perform preprocessing before hyperopt when possible #1416

Closed
tgaddair opened this issue Oct 24, 2021 · 0 comments · Fixed by #1415
Closed

[ray] Perform preprocessing before hyperopt when possible #1416

tgaddair opened this issue Oct 24, 2021 · 0 comments · Fixed by #1415
Labels
feature New feature or request
Projects

Comments

@tgaddair
Copy link
Collaborator

Currently, we perform preprocessing for every trial separately regardless of whether any preprocessing params are being tuned. This is inefficient, and also seems to cause a deadlock when using RayDatasets with dynamic resource allocation during tuning.

Instead, we can perform preprocessing up front, and then reuse the RayDataset among all the trials. It may be the case that we need to persist to parquet as well, otherwise it may cause issues when multiple trials attempt to run the pipeline simultaneously.

@tgaddair tgaddair added the feature New feature or request label Oct 24, 2021
@tgaddair tgaddair added this to To do in Ray via automation Oct 24, 2021
Ray automation moved this from To do to Done Oct 30, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request
Projects
Ray
Done
Development

Successfully merging a pull request may close this issue.

1 participant