Re:Ansible 2.0 released
by skywhopper on Tuesday January 12, 2016 @05:09PM
(#10890796)
Love Ansible, but am I the only one who has found 2.0 to be unbearably slow? Some patterns I use may now be anti-patterns I should factor out, but even with some optimizations, I'm finding Ansible 2.0 to be 3-4x slower than 1.9. Maybe it has to do with # of hosts or variable field depth, but it's really really depressing.
[ Parent
| on HN ]
I also use and really appreciate Ansible. I tried out 2.0 yesterday and found the sheer number of incompatiblities with my existing work very frustrating.
I wish there was a clear migration path of exactly what needs to be changed to port things from 1.x -> 2.0, rather than just many cycles of "try it and patch".
Re:Ansible 2.0 released
by jeffwidman on Tuesday January 12, 2016 @07:13PM
(#10891409)
As another Ansible user contemplating the 1.9-->2.0 migration, I'd appreciate if you would submit PRs updating the porting guide with stuff that you hit that wasn't already mentioned:https://github.com/ansible/ansible/blob/devel/docsite/rst/po...
Thank you for pointing me to the porting guide doc! If only they'd linked to that in the article ;)
Re:Ansible 2.0 released
by LukeHoersten on Tuesday January 12, 2016 @10:25PM
(#10892144)
Do you have connection pipelining enabled?:
[ssh_connection] pipelining = True
Ansible 2 is extremely fast for me.
Re:Ansible 2.0 released
by skywhopper on Wednesday January 13, 2016 @04:50PM
(#10897831)
Yes, pipelining is on. I've been doing some further testing and I suspect some of the nested roles we're using are the source of the slowness, because for simple playbooks and simple tasks, the speed is comparable (Ansible 1.9 still comes in a little faster, unless I enable the `free` strategy in 2.0).