Streamlining Big Data Workflows with Memoization & Work Avoidance
summary
Argo Workflows uses memoization via ConfigMaps to skip steps entirely by storing a key, outputs and a max_age so repeated runs drop pod startup time to zero on cache hits; artifacts store paths while parameters embed values and risk the ~1MB etcd configmap limit and eviction. As an alternative, work avoidance with marker files keeps logic in the container and still requires pod startup. Pure, input‑derived steps are safe to cache; nonpure steps need careful keys and expiration.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:06Memoization reduces work
- 2:31Memoization in Argo Workflows
- 4:15Memoization keys skip steps
- 6:23Memoizing workflows and DAGs
- 7:27ConfigMaps caching limits
- 9:16Memoized DNA sequencing example
- 11:27Work avoidance technique
- 13:13ConfigMaps size limits
- 15:03Pure steps memoization rules
- 16:54Risks of impure steps
- 17:16Further reading
- 17:37Q&A
related talks
20mDemystifying Argo Workflows: An Architectural Deep Dive
10mScaling Time Series Analysis With Argo Workflows: Patterns and Practi...
23mMastering Argo Workflows at Scale: A Practical Guide to Scalability Excellence
21mBreaking the 1.5MB Barrier: Running Large Metaflow Flows with Argo for AI/ML Workloa...
25mLeveraging Argo Workflows and Argo Events for Cloud Agnostic Enter...
27mEmpowering Autonomy: BYD's Journey Taming Million-Task Scale With Argo...
25mPanel: Argo for ML: Achieving Scalability and User Experience
22mBuilding AutoML Pipelines With Argo Workflows and Katib
