![cpu throttled cpu throttled](https://forum.donanimhaber.com/store/ab/b5/29/abb52950e95c230f8acc69beb78edcd4.png)
This allowed us to optimise the infrastructure further for getting maximum performance out of it. We adopted USE-RED dashboards for our services to help us track critical metrics. The services are then exposed via ingress for developers to use with the test suite or use as the endpoint for debug apps for application testing. Mft is used to create new namespaces in Kubernetes and inject necessary dependencies from Vault and Consul.Īll the services necessary to run a copy of Grofers are then deployed via common Jenkins setup.
![cpu throttled cpu throttled](https://www.techilife.com/wp-content/uploads/2021/03/CPU-Throttling.png)
To achieve this, we have developed an in-house tool called mft. This is what we internally call ‘Grofers-in-a-namespace’. This led us to adopt a design where each developer has his own namespace with all services deployed in an isolated environment for testing and debugging. Therefore developers cannot work on multiple services at the same time in the same namespace. BackgroundĪt Grofers, we follow a microservice architecture where all critical components like payments, carts, inventory, etc. 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. 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. We don’t just deploy applications on Kubernetes in production, but we also use it heavily for our CI/CD and developer infrastructure. Kubernetes is a crucial part of our infrastructure. CPU Throttling in Kubernetes: A Postmortem