Why we switched our philosophy from Ops to Infrastructure

This post details a philosophical shift from a reactive 'Operations mindset' to a proactive 'Infrastructure mindset' for managing GitLab's performance and scalability. Key steps include focusing on infrastructure from a development perspective, spotting patterns through time-based metrics, understanding performance gaps, aligning resources effectively, automating manual tasks, and iterating on solutions. It also describes a specific win in improving SSH Git access time by debugging and resolving issues related to `authorized_keys` file linear search, worker restarts, HTTP request queuing, and D-Bus connection limits. The post also lists the toolbox used for these efforts, including Chef, Prometheus, Grafana, ELK stack, and Sentry.