From cb1cabbfe652bcfdda4a116c290d8474c3f1f4e1 Mon Sep 17 00:00:00 2001 From: Renat Akhmerov Date: Fri, 27 Apr 2018 20:00:36 +0700 Subject: [PATCH] Release note for workflow environment optimizations Change-Id: Ieff4887384a4f8fa0eb52a6255f3e4402dbf1d8e Related-Bug: #1757966 --- ...vironment_optimizations-deb8868df3f0dc36.yaml | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) create mode 100644 releasenotes/notes/workflow_environment_optimizations-deb8868df3f0dc36.yaml diff --git a/releasenotes/notes/workflow_environment_optimizations-deb8868df3f0dc36.yaml b/releasenotes/notes/workflow_environment_optimizations-deb8868df3f0dc36.yaml new file mode 100644 index 000000000..6ad7f0147 --- /dev/null +++ b/releasenotes/notes/workflow_environment_optimizations-deb8868df3f0dc36.yaml @@ -0,0 +1,16 @@ +--- +fixes: + - Mistral was storing, in fact, two copies of a workflow environment, + one in workflow parameters (the 'params' field) and another one in + a context (the 'context' field). Now it's stored only in workflow + parameters. It saves space in DB and increases performance in case + of big workflow environments. + - Mistral was copying a workflow environment into all of their sub + workflows. In case of a big workflow environment and a big number + of sub workflows it caused serious problems, used additional space + in DB and used a lot of RAM (e.g. when the 'on-success' clause has + a lot of tasks where each one of them is a subworkflow). Now it is + fixed by evaluating a workflow environment through the root execution + reference. + +