Thanks for your suggestion Brian. As I stated, I've looked at the CPU & RAM usage, they were perfectly fine. I'll see if network is limiting anything, but I have some doubts: it's a entreprise wired LAN, and the logical behaviour of a bandwith limited ansible would be:
- phase 1: many DNS requests, some of them would be slow, timeout maybe, and be reemitted - phase2: begin some SSH connection, but still struggling with DNS requests - phase 3: DNS requests have mainly been done, SSH connections now struggles to be established But it's not what I've seen with wireshark (see previous message, only small batches of dozens of DNS requests at a time, after an initial phase with very few DNS requests). The idea of a mono threaded resolver is really interesting. You mean at the control machine OS level? Le mercredi 5 août 2015 18:15:14 UTC+2, Brian Coca a écrit : > > no, by resources I meant cpu, ram, bandwith, etc, slow dns resolution > might make some forks and the overall performance degrade but it > should not factor too much on how many ssh connections you can open at > the same time, unless you are using a single proc/thread resolver. > > > -- > Brian Coca > -- 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 ansible-project+unsubscr...@googlegroups.com. To post to this group, send email to ansible-project@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/33e6b4d7-75ac-41a6-8c67-6a7c366fec4c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
