From e0fe184c8947fbb53325e54b2d5dd90d59a40993 Mon Sep 17 00:00:00 2001 From: Ryan Richard Date: Wed, 14 Apr 2021 08:35:04 -0700 Subject: [PATCH] Relax cpu limit on ldap server a little to make it start faster - Allowing it to use more CPU during startup decreases startup time from about 25 seconds (on my laptop) down to about 1 second. --- test/deploy/tools/ldap.yaml | 12 ++++++------ test/deploy/tools/proxy.yaml | 4 ++-- 2 files changed, 8 insertions(+), 8 deletions(-) diff --git a/test/deploy/tools/ldap.yaml b/test/deploy/tools/ldap.yaml index 9bd49df0..0df509ec 100644 --- a/test/deploy/tools/ldap.yaml +++ b/test/deploy/tools/ldap.yaml @@ -148,18 +148,18 @@ spec: containerPort: 1636 resources: requests: - cpu: "10m" + cpu: "100m" #! one-tenth of one CPU memory: "64Mi" limits: - cpu: "10m" + cpu: "200m" #! slapd needs a reasonable amount of CPU during initial startup or else it is slow to start memory: "64Mi" readinessProbe: tcpSocket: port: ldap - initialDelaySeconds: 25 #! typically takes about 30 seconds to start - timeoutSeconds: 120 - periodSeconds: 5 - failureThreshold: 6 + initialDelaySeconds: 2 + timeoutSeconds: 90 + periodSeconds: 2 + failureThreshold: 9 env: #! Example ldapsearch commands that can be run from within the container based on these env vars. #! These will print the whole LDAP tree starting at our root. diff --git a/test/deploy/tools/proxy.yaml b/test/deploy/tools/proxy.yaml index 3a70b3dd..ae293a8a 100644 --- a/test/deploy/tools/proxy.yaml +++ b/test/deploy/tools/proxy.yaml @@ -32,10 +32,10 @@ spec: containerPort: 3128 resources: requests: - cpu: "10m" + cpu: "100m" #! one-tenth of one CPU memory: "64Mi" limits: - cpu: "10m" + cpu: "100m" #! one-tenth of one CPU memory: "64Mi" volumeMounts: - name: log-dir