Release note for batched evaluation of final workflow context
Change-Id: I861d99c5a4aa6bf1f80b2eacf5dd7d0a110aef61
This commit is contained in:
parent
644f705345
commit
5073274dd1
@ -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.
|
Loading…
Reference in New Issue
Block a user