From 219f82f657f3693912c033800fc7ce3f0ed4f5d6 Mon Sep 17 00:00:00 2001 From: Alan Clucas Date: Fri, 14 Jul 2023 17:57:38 +0100 Subject: [PATCH] docs: Finish describing memoization Complete my sentence from PR #11257 Signed-off-by: Alan Clucas --- docs/work-avoidance.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/work-avoidance.md b/docs/work-avoidance.md index e2eeb913da02..726087ae7097 100644 --- a/docs/work-avoidance.md +++ b/docs/work-avoidance.md @@ -4,7 +4,7 @@ You can make workflows faster and more robust by employing **work avoidance**. A workflow that utilizes this is simply a workflow containing steps that do not run if the work has already been done. -This technique is similar to [memoization](memoization.md) but they have distinct use cases. Work avoidance is totally in your control and you make the decisions as to have to skip the work. [Memoization](memoization.md) is a feature of Argo Workflows to automatically skip steps which generate outputs - it is designed +This technique is similar to [memoization](memoization.md) but they have distinct use cases. Work avoidance is totally in your control and you make the decisions as to have to skip the work. [Memoization](memoization.md) is a feature of Argo Workflows to automatically skip steps which generate outputs - it is designed for pure steps which only generate output based on their inputs. This simplest way to do this is to use **marker files**.