Commit 67ff762b authored by David Wilson's avatar David Wilson

issue #139: docs: remove note about bad buffering

parent eba12e2e
...@@ -126,10 +126,9 @@ High Risk ...@@ -126,10 +126,9 @@ High Risk
* Transfer of large (i.e. GB-sized) files using certain Ansible-internal APIs, * Transfer of large (i.e. GB-sized) files using certain Ansible-internal APIs,
such as triggered via the ``copy`` module, will cause corresponding temporary 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 memory and CPU spikes on both host and target machine, due to delivering the
file as a single large message, and quadratic buffer management in both file as a single large message. If many machines are targetted with a large
sender and receiver. If many machines are targetted with a large file, the file, the host machine could easily exhaust available RAM. This will be fixed
host machine could easily exhaust available RAM. This will be fixed soon as soon as it's likely to be tickled by common playbook use cases.
it's likely to be tickled by common playbook use cases.
* Situations may exist where the playbook's execution conditions are not * Situations may exist where the playbook's execution conditions are not
respected, however ``delegate_to``, ``connection: local``, ``become``, respected, however ``delegate_to``, ``connection: local``, ``become``,
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment