This is an automated email from the ASF dual-hosted git repository.
heneveld pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/brooklyn-docs.git
The following commit(s) were added to refs/heads/master by this push:
new 2b9acbbd expand slightly on optimizing workflow
2b9acbbd is described below
commit 2b9acbbd3a6c4ccf6cdf318750ab10e69aaff9c2
Author: Alex Heneveld <[email protected]>
AuthorDate: Tue Jun 13 10:27:49 2023 +0100
expand slightly on optimizing workflow
---
guide/blueprints/workflow/settings.md | 8 +++++---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/guide/blueprints/workflow/settings.md
b/guide/blueprints/workflow/settings.md
index 6bc480a8..2f76ff31 100644
--- a/guide/blueprints/workflow/settings.md
+++ b/guide/blueprints/workflow/settings.md
@@ -486,13 +486,15 @@ performance can be dramatically improved by following
these tips:
* Optimize external calls to return the minimal amount of information needed
* Use `jq` to filter when using `ssh` or `container` steps
- * Pass filter argumetns to `http` endpoints that accept them
- * Use small page sizes with `retry from` steps
+ * Pass filter arguments to `http` endpoints that accept them
+ * Loop over small page sizes (e.g. 20 records per cycle from `http`) using
`retry from` steps
* Optimize the data which is stored
* Override the `output` on `ssh` and `http` steps to remove unnecessary
objects;
for example `http` returns several `content*` fields, and often just one
is needed.
Simply settings `output: { content: ${content} }` will achieve this.
* Set `retention: 1` or `retention: 0` on workflows that use a large amount
of information
- and can simply be replayed from the start
+ and can simply be replayed from the start; additionally `retention:
disabled` can be used
+ to prevent any persistence (even for ongoing workflows), but only for
workflows that do
+ not acquire any `lock`
