Yep, it's primarily useful for *longer* playbooks, rather than a
parallelism thing (completely unrelated to the number of hosts), and shows
greater dividends over more latent connections.

All being said the alternate SSH transport being developed now (-c ssh_alt,
to become the new -c ssh once completed with testing) may obviate the need
for accelerate mode in many cases.




On Mon, Dec 23, 2013 at 4:11 PM, Brian Coca <[email protected]> wrote:

> not your setup costs, the (time) cost of setting up the socket server on
> the 'targets' and networking them, for you its just a connection: <plugin>.
>
> it IS faster when dealing with average to large playbooks, but it stands
> to reason that it will be slower for a single task, as it uses ssh to
> connect initially to setup the accelerated socket server and then run the
> task, vs ssh and running the task.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Ansible Project" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To post to this group, send email to [email protected].
> For more options, visit https://groups.google.com/groups/opt_out.
>



-- 
Michael DeHaan <[email protected]>
CTO, AnsibleWorks, Inc.
http://www.ansibleworks.com/

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to