3 years ago

Category: Kubernetes, Infrastructure

While developing our CI/CD infrastructure, we dealt with a particular performance issue of our dev and CI environments taking up a lot of time to spin up. In this article, we will attempt to go deep into the issue that degraded performance of our applications and how we finally solved that issue.

Also, some of our Jenkins jobs took a lot of time to create the environments and get them ready, something that we previously did not account for.

Furthermore, we observed that in our CI and dev environments, this was happening a lot with some specific containers at startup time — these were containers where we were running some kind of CPU intensive operation at startup time.

Based on this exercise, we came up with an application profiling plan for our major applications and added CPU throttling to one of our core suspects of poor application performance.