---
title: "Discussion on \"How I Cut Our CI/CD Pipeline from 35 to 5 Minutes (And Saved the Team's Sanity)\" | Hashnode"
description: "Discussion on \"How I Cut Our CI/CD Pipeline from 35 to 5 Minutes (And Saved the Team's Sanity)\". How we slashed CI/CD pipeline time for a massive monorepo by identifying I/O bottlenecks and tuning OPcache for CLI"
url: "https://hashnode.com/posts/optimizing-monorepo-ci-cd-pipeline/69ef085198160f464f60a6d6"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [How I Cut Our CI/CD Pipeline from 35 to 5 Minutes (And Saved the Team's Sanity)](https://blog.iamdev.pl/optimizing-monorepo-ci-cd-pipeline?utm_source=hashnode&utm_medium=feed)

How we slashed CI/CD pipeline time for a massive monorepo by identifying I/O bottlenecks and tuning OPcache for CLI

Apr 27 · 11 min read · blog.iamdev.pl  
Read the article

-   [#php](https://hashnode.com/tag/php)
-   [#ci-cd](https://hashnode.com/tag/ci-cd)
-   [#aws](https://hashnode.com/tag/aws)
-   [#aws-ec2](https://hashnode.com/tag/aws-ec2)
-   [#gitlab](https://hashnode.com/tag/gitlab)
-   [#composer](https://hashnode.com/tag/composer)
-   [#performance](https://hashnode.com/tag/performance)
-   [#performance-optimization](https://hashnode.com/tag/performance-optimization)
-   [#php8](https://hashnode.com/tag/php8)
-   [#phpunit](https://hashnode.com/tag/phpunit)
-   [#docker](https://hashnode.com/tag/docker)
-   [#optimization](https://hashnode.com/tag/optimization)

## Written by

[Michał Iżewski](https://hashnode.com/@michal-izewski)

@michal-izewski · Gdansk, Poland

  
[View profile](https://hashnode.com/@michal-izewski)

Backend engineer · production systems, reliability & performance (AWS, CI/CD, distributed systems)

Backend engineer with 18+ years building and running production systems. I started deep in the PHP world and grew into a polyglot, infrastructure-aware engineer; these days I care less about the language and more about how a system behaves under load, where it breaks, and what the trade-offs actually cost. Strong on reliability, performance, and the operational side: AWS, CI/CD, the things that only show up in production. I write these posts mostly as case studies for myself: take a real problem, understand the system underneath, make a decision, and spell out what it cost. One concrete example: I cut a CI pipeline from 30+ minutes to under 5 by chasing I/O bottlenecks instead of throwing hardware at it.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.