Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
ansible: poor performance with multiple targets #250
Per user report in #249, now that >100 targets is possible growing pains are starting to rear their heads.
Likely low hanging fruit:
referenced this issue
May 15, 2018
Hi @sharph, if you're feeling adventurous, I have 3 Ansible patches in https://github.com/dw/ansible/tree/dmw that reduce runtime almost 40% for 10 host runs. These don't help explain why Mitogen is slower, but I'm struggling to profile that yet because Ansible sucks so much in these cases :)
Still "work in progress", but if you're interested in kicking the tires, it would be very useful.
Edit: whups, the complete branch is https://github.com/dw/ansible/tree/dmw .. devel is just a doc patch
Long time no update :) I have not stopped working on very large run performance, but unfortunately most of the important work cannot exist in a third-party extension.
Meanwhile, over the past months quite a few big fixes have been found -- two in particular were addressed in 0.2.3, relating to context switching overhead due to the use of threading, and one that concentrated a lot of redundant CPU usage in the connection multiplexer process.
I also have a separate branch that supports per-CPU multiplexer processes, however it is a little stale at this point. If you are still interested in this kind of work, and the newer fixes don't help much -- please say! I can at least see if the per-CPU work helps in your case, and if so, we could see about merging it into the stable series.