I have a WF that run 100 iterations where at each iteration that same process is excuted. At the end we collect the results on the loop end. I have choose to save the data in the desk.
I dont know why as the iterations in increasing the WF memory is incresing and after while it frezzes.
See WF image
Hi @malik -
A few questions. First, does the workflow successfully complete for a small number of iterations, or does it fail no matter how many there are? Second, are you able to isolate the freeze to a particular node - that is, does it happen at the same place every time you execute? Lastly, have you tried increasing the memory available to KNIME in knime.ini?
That’s good to know - I didn’t realize that you were using a parallel chunk loop node. That’s from KNIME Labs, so it’s possible you’ve discovered some unexpected behavior from the node. I’ll check with some of our developers and see what I can find out.
Are you able to share the portion of the workflow that contains the parallel chunk node? I don’t see it in the screenshot above, and a workflow would help troubleshoot.
It’s no surprise that you need more memory if you are processing multiple chunks in parallel. All nodes are essentially duplicated as many times as there are parallel executions.
Is till didn’t get the answer why the WF memory that i watch through Task Manger is increasing ?
This is a very simple example WF- You can download the data file from :
- If you run for the first time 100 iteration and then run it again you keep see the WF memory is incressing
- Why the WF is incressing where each time we work on almost the dame size of teh data and save the collection into the desk?
Did you look to the issue of increasing WF memery ?
Also how one can rest the WF memery after exceutaion ?
Hi @malik -
I’ll have to check with the devs about the memory question and get back to you.