Comment 3 for bug 1885750

Hello,
I did some experiments to improve the current state.
Key is the memory consumption of one process. This can be difficult/ time demanding to solve.

Secondary is the number of processes/forks. This is much easier to change. It is possible to reduce number of forks for problematic playbooks.
New version of ansible - 2.9 is providing keyword "throttle". Official description is here:https://docs.ansible.com/ansible/latest/user_guide/playbooks_strategies.html

"The second keyword to affect execution is throttle, which can also be used at the block and task level. This keyword limits the number of workers up to the maximum set via the forks setting or serial."

Reduced number of processes is just workaround, not solution of the problem.