From e1a0e09f6273631438a3e0c24605285cde07a52b Mon Sep 17 00:00:00 2001 From: Maja Massarini Date: Wed, 8 May 2024 15:21:48 +0200 Subject: [PATCH] Lower cpu requests The previous cpu limit increase 7b88605f16ee5a7f52ad06bef4d462eab940d645 should be enough. The cluster running our pods should have enough resources to satisfy our needs without us blocking the resources. --- playbooks/deploy.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/playbooks/deploy.yml b/playbooks/deploy.yml index 5e92239..0ccf952 100644 --- a/playbooks/deploy.yml +++ b/playbooks/deploy.yml @@ -253,7 +253,7 @@ # Short-running tasks are just interactions with different services. # They should not require a lot of memory/cpu. worker_requests_memory: "320Mi" - worker_requests_cpu: "200m" + worker_requests_cpu: "80m" worker_limits_memory: "640Mi" worker_limits_cpu: "400m" ansible.builtin.include_tasks: tasks/k8s.yml @@ -285,7 +285,7 @@ # cloning repos is memory intensive: glibc needs 300M+, kernel 600M+ # during cloning, we need to account for git and celery worker processes worker_requests_memory: "384Mi" - worker_requests_cpu: "400m" + worker_requests_cpu: "100m" worker_limits_memory: "1024Mi" worker_limits_cpu: "600m" ansible.builtin.include_tasks: tasks/k8s.yml