cmd/coordinator: triple the memory allocation
The coordinator often hovers at under 2 GB of memory use when not
in active use, but has been observed to reach and exceed its 12 GB
allocation during times of heavy parallel builds, especially when
there are concurrent changes to release branches (as sometimes
happens during the release process).
Since there's only one instance of the coordinator and it has a real
need today, it's relatively inexpensive to give it more memory until
we make progress on understanding and possibly reducing it. Having
the coordinator not restart while many builds are in progress will
help reduce computational costs and waiting times.
For golang/go#51057.
Change-Id: I530cefc8aa401843684eea48a6a5d34072622fd5
Reviewed-on: https://go-review.googlesource.com/c/build/+/409594
Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org>
Reviewed-by: Carlos Amedee <carlos@golang.org>
Reviewed-by: Heschi Kreinick <heschi@google.com>
TryBot-Result: Gopher Robot <gobot@golang.org>
diff --git a/cmd/coordinator/deployment-prod.yaml b/cmd/coordinator/deployment-prod.yaml
index af23869..14f2161 100644
--- a/cmd/coordinator/deployment-prod.yaml
+++ b/cmd/coordinator/deployment-prod.yaml
@@ -30,10 +30,10 @@
resources:
requests:
cpu: "4"
- memory: "12Gi"
+ memory: "32Gi"
limits:
cpu: "6"
- memory: "16Gi"
+ memory: "36Gi"
---
apiVersion: v1
kind: Service
