A walkthrough of building an automated CI framework to periodically benchmark etcd performance and track regressions over time. The setup uses Red Hat Ansible Automation Platform for orchestration, Podman for containerized benchmark isolation, and Horreum (an open source performance repository) for storing results, visualizing trends, and detecting anomalies. The article covers the full workflow: Ansible playbook structure, Podman Containerfile that builds Go from source and compiles etcd, key metrics collected (throughput and latency for PUT and STM operations), and Horreum configuration including schema creation, label definition, and change detection thresholds. The primary motivation is catching performance regressions in Red Hat's Go toolchain builds early, since etcd exercises a broad range of Go runtime features.

Table of contents
Building blocks: Ansible, Podman, and HorreumThe workflowStructure of the Ansible playbookPodman container configurationConfigure HorreumIt's time to benefit from early warningsSort: