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

Enable caching of pipeline steps #151

Open
tarekoraby opened this issue Apr 10, 2024 · 0 comments
Open

Enable caching of pipeline steps #151

tarekoraby opened this issue Apr 10, 2024 · 0 comments

Comments

@tarekoraby
Copy link

Quite often, pipeline steps don't change between runs. For example, a pre-processing step on the same input dataset will always generate the same processed output. In those cases, it would be beneficial not to waste time and resources re-executing the step. And while the Valohai UI offers an option that allows users to manually reuse steps from previous runs, this manual option

  1. can be missed by less experienced users
  2. doesn't help in cases where the pipeline should be automatically triggered.

Thus, it would be nice to have the option to enable caching on specific steps. When this caching is enabled, Valohai should try to find a previous execution of the same step that has the same inputs + parameters. If such execution is found, the output from this previous execution will be reused rather than re-running the step again.

However, there might be situations where the step should be cached most of the time, except that it should be occasionally rerunning the whole step. For example, a pre-processing step might be programmatically retrieving data from a remote API. Most of the time, this remote data remains unchanged. But occasionally (say once a week), the API should be rechecked for updates. In such a scenario, it would be essential to offer the option to force run a step, even if caching is enabled for that step.

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