From 8f859430831ee94eabd8d70cda9e9dfb530e3750 Mon Sep 17 00:00:00 2001 From: David Wilson Date: Tue, 13 Mar 2018 18:45:26 +0545 Subject: [PATCH] issue #139: mention relating buffering issue --- docs/ansible.rst | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/docs/ansible.rst b/docs/ansible.rst index fec2318a..b34d2b03 100644 --- a/docs/ansible.rst +++ b/docs/ansible.rst @@ -123,9 +123,10 @@ High Risk * Transfer of large (i.e. GB-sized) files using certain Ansible-internal APIs, such as triggered via the ``copy`` module, will cause corresponding temporary memory and CPU spikes on both host and target machine, due to delivering the - file as a single large message. If many machines are targetted with a large - file, the host machine could easily exhaust available RAM. This will be fixed - soon as it's likely to be tickled by common playbook use cases. + file as a single large message, and quadratic buffer management in both + sender and receiver. If many machines are targetted with a large file, the + host machine could easily exhaust available RAM. This will be fixed soon as + it's likely to be tickled by common playbook use cases. * Situations may exist where the playbook's execution conditions are not respected, however ``delegate_to``, ``connection: local``, ``become``,