From 5073274dd1f15a59a07da99f3aa387fb6e5d51dc Mon Sep 17 00:00:00 2001 From: Renat Akhmerov <renat.akhmerov@gmail.com> Date: Fri, 20 Apr 2018 18:32:19 +0700 Subject: [PATCH] Release note for batched evaluation of final workflow context Change-Id: I861d99c5a4aa6bf1f80b2eacf5dd7d0a110aef61 --- ...ext_evaluation_with_batches-6292ab64c131dfcc.yaml | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 releasenotes/notes/wf_final_context_evaluation_with_batches-6292ab64c131dfcc.yaml diff --git a/releasenotes/notes/wf_final_context_evaluation_with_batches-6292ab64c131dfcc.yaml b/releasenotes/notes/wf_final_context_evaluation_with_batches-6292ab64c131dfcc.yaml new file mode 100644 index 000000000..e1bcc93b8 --- /dev/null +++ b/releasenotes/notes/wf_final_context_evaluation_with_batches-6292ab64c131dfcc.yaml @@ -0,0 +1,12 @@ +--- +fixes: + - Evaluation of final workflow context was very heavy in cases + when the workflow had a lot of parallel tasks with large + inbound contexts. Merging of those contexts in order to + evaluate the workflow output consumed a lot of memory. + Now this algorithm is rewritten with batched DB query and + Python generators so that GS has a chance to destroy + objects that have already been processed. Previously all + task executions had to stay in memory until the end of the + processing. The result is that now it consumes 3 times less + memory on heavy cases. \ No newline at end of file