Ansible Playbook Optimization: Write Efficient Playbooks | DevOpsNess

Ansible Playbook Optimization: Writing Efficient Playbooks

Optimized playbooks run faster and are more maintainable. This guide covers optimization techniques.

Parallel Execution #

yaml.yaml

# ansible.cfg
[defaults]
forks = 10
host_key_checking = False

# Playbook
- hosts: all
  serial: 5  # Run on 5 hosts at a time
  tasks:
    - name: Install packages
      apt:
        name: "{{ item }}"
      loop:
        - nginx
        - python3

Fact Caching #

yaml.yaml

# ansible.cfg
[defaults]
fact_caching = jsonfile
fact_caching_connection = /tmp/ansible_facts
fact_caching_timeout = 3600

Efficient Tasks #

yaml.yaml

# Use modules instead of shell
- name: Install package
  apt:
    name: nginx
    state: present
  # Instead of: shell: apt-get install nginx

# Use handlers
handlers:
  - name: restart nginx
    systemd:
      name: nginx
      state: restarted

tasks:
  - name: Update config
    template:
      src: nginx.conf.j2
      dest: /etc/nginx/nginx.conf
    notify: restart nginx

Best Practices #

Use modules instead of shell
Enable fact caching
Use parallel execution
Organize with roles
Use conditionals wisely

Conclusion #

Optimize playbooks by using modules, enabling caching, and running tasks in parallel for better performance.

For Ansible Playbook Optimization: Writing Efficient Playbooks, define pre-deploy checks, rollout gates, and rollback triggers before release. Track p95 latency, error rate, and cost per request for at least 24 hours after deployment. If the trend regresses from baseline, revert quickly and document the decision in the runbook.

Keep the operating model simple under pressure: one owner per change, one decision channel, and clear stop conditions. Review alert quality regularly to remove noise and ensure on-call engineers can distinguish urgent failures from routine variance.

Repeatability is the goal. Convert successful interventions into standard operating procedures and version them in the repository so future responders can execute the same flow without ambiguity.