"Personally, I think there's some merit in optimizing the paramiko transport, because Ansible knows best when a channel is going to be reused, and when it can be closed. "
Keeping these open is possible but requires "fork affinity" the idea that the next time the host is dealt with, it goes to the same fork. I really think openssh is the one true way, it's only kept around because RHEL hasn't updated their OpenSSH clients yet to support CP. On Wed, Nov 27, 2013 at 1:00 PM, Jerome Wagner <[email protected]> wrote: > yes the control machine is not located on premises (but i do not use ec2) > In fact I try on purpose to control hosts that are located at several > distinct providers so I use my laptop as a control machine. > I expect the latency to be greater but I thought that accelerate would. > > Just to understand, accelerate works by doing only 1 connection into 5099 > and then send all the tasks inside this tunnel or is there still 1 > connection on 5099 per task ? > > my ping to the remote hosts is around 50ms. > > what should I expect to reach as a correct timing for 10 x command: echo > on a remote host ? > > Thank you > > Le mercredi 27 novembre 2013 18:19:52 UTC+1, Michael DeHaan a écrit : >> >> The debug module doesn't do anything with the remote host, BTW. >> >> The script module pushes a remote script and executes it, the command >> module pushes the command module and executes some arguments -- they are >> slightly different in the way those work. >> >> Once piece of advice I usually give to people is if managing machines >> inside EC2, but your control machine inside EC2 -- the networking can be >> quite bad externally. >> >> The fact that accelerate doesn't offer any benefits for a multi-task >> playbook is curious, but a sign of other networking difficulties. >> >> >> >> On Wed, Nov 27, 2013 at 12:15 PM, Michael DeHaan <[email protected] >> > wrote: >> >>> Sounds like you have some interesting DNS or network problems to figure >>> out. >>> >>> >>> >>> >>> >>> >>> On Wed, Nov 27, 2013 at 12:11 PM, Jerome Wagner <[email protected]>wrote: >>> >>>> Hello, >>>> >>>> I am trying to speed up my ansible installation. I went from 20 >>>> minutes execution to 10 minutes by switching from centos6.4(paramiko) to >>>> fedora19(ssh+control persist). Enabling accelerate=true did not bring any >>>> speed up (??). >>>> >>>> Here are the tests I ended up doing ; Can you help me understand the >>>> difference between the *debug:*, *script:* and *command:* measurements >>>> and what are my options to speed things up ? >>>> >>>> what are your numbers on the same tests ? how can I measure what is a >>>> reasonable time from an ansible point of view versus bad configuration / >>>> bad vm hosting choices ? >>>> >>>> what do you think is taking 3sec+ per task in accelerate mode with >>>> *command: >>>> echo "ping" ? *knowing that I have approximately 200 tasks in my >>>> actual playbook (output from --list-tasks), 200 tasks * 3 sec ~ 10 minutes >>>> which is what I am observing. >>>> >>>> thank you for your help ! >>>> Jerome >>>> -- >>>> *test procedure :* >>>> >>>> * a simple playbook repeating 10 times a simple task on all hosts (3 >>>> remote hosts: cheap ovh vm) >>>> * connection to remotes via ssh keys >>>> * 2 runs only keep the values for the second run. >>>> >>>> - hosts: all >>>> gather_facts: no >>>> tasks: >>>> - debug: msg="ping" >>>> .. repeated 10 times >>>> >>>> *results:* >>>> >>>> *10 x debug: msg="ping" * >>>> * ssh : 0.8 seconds >>>> * accelerate : 1.5 seconds >>>> >>>> *10 x script: echo.sh *(the script only does echo "ping") >>>> * ssh: 15 seconds >>>> * accelerate: 10 seconds >>>> >>>> *10 x command: echo "ping"* >>>> * ssh : 41 seconds >>>> * accelerate : 33.8 seconds >>>> >>>> >>>> >>>> -- >>>> 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]. >>>> >>>> For more options, visit https://groups.google.com/groups/opt_out. >>>> >>> >>> >>> >>> -- >>> Michael DeHaan <[email protected]> >>> >>> CTO, AnsibleWorks, Inc. >>> http://www.ansibleworks.com/ >>> >>> >> >> >> -- >> 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]. > 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]. For more options, visit https://groups.google.com/groups/opt_out.
