There's no getting around the fact that winrm is a much slower protocol 
than ssh. Those numbers seem unreasonably high tho. Any chance you're using 
a local ansible control node against cloud-based windows servers?

You could also consider speeding up your playbooks using the "forks" 
(http://www.ansible.com/blog/ansible-performance-tuning)

On Friday, October 9, 2015 at 3:46:52 PM UTC+2, Michael Baydoun wrote:
>
> A few of our windows hosts take 20-30 seconds to gather facts, and that's 
> the good news.  The other hosts take > 1 minute just to gather facts.  
> When run with -vvvv, it appears to me that every winrm step just takes a 
> long time.
>
> Has anyone run into this?  Suggestions?  Adding each windows host to our 
> inventory is causing painful increases in site.yml run time.
> Note: running ansible 1.9.2, and hoping 2.0 will improve the situation 
> when it's released
>
> I wrote a test to gather run times for fact gathering, results for windows 
> hosts below (with hostnames removed)
>
> min:sec:hundredths 
> 0:26.66
> 1:13.46
> 1:15.47
> 1:14.77
> 1:33.89
> 0:32.68
> 2:44.04
> 1:34.65
> 1:30.29
> 1:25.71
> 0:29.66
> 0:25.86
> 1:08.95
> 1:09.38
> 0:21.88
> 0:24.47
>
>

-- 
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].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/52345e1c-fe15-477d-9e72-799ec00b5814%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to