# Ansible connects on each task

**URL:** <https://forum.ansible.com/t/ansible-connects-on-each-task/12432>\
**Category:** Ansible Project\
**Tags:** ansible-project\
**Created:** [February 28, 2013, 12:54pm UTC](https://forum.ansible.com/t/ansible-connects-on-each-task/12432 "2013-02-28T12:54:09Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Michael\_DeHaan](https://avatars.discourse-cdn.com/v4/letter/m/c4cdca/32.png) [@Michael\_DeHaan](https://forum.ansible.com/u/Michael_DeHaan)\
**Post date:** [February 28, 2013, 12:54pm UTC](https://forum.ansible.com/t/ansible-connects-on-each-task/12432/1 "2013-02-28T12:54:09Z")

</div>

This is just a debug message. What ansible calls a connection is a  
Connection object, not the actual connection.

If you use "-c ssh" and have a client that supports Control Persist,  
ansible will reuse connections just fine.

Fireball mode works in the same way.

It is true that paramiko does not currently hold connections open,  
because of the way we use it with multiprocessing and plays, and  
sharing connections across forks.

However, paramiko is pretty darn fast, and approaches the speed of  
Control Persist, even that way.