Greatly increase the upper limit of proxy instances in production (#2259)

From our investigation, the Monday night WHOIS storm does not cause any
strain to the backend system. The backend latency metrics are all well within
the limits. The latency measured from the proxy matches observed latency
by the prober, and we see that the "used" CPU is 1.5x of "requested" CPU
during the time when the latency is above the threshold.

Making this change hopefully removes the proxy as the bottleneck and
ameliorate the pages.
This commit is contained in:
Lai Jiang 2023-12-20 15:37:29 -05:00 committed by GitHub
parent fb4c5b457d
commit 08285f5de7
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23

View file

@ -46,5 +46,5 @@ spec:
apiVersion: apps/v1
kind: Deployment
name: proxy-deployment
maxReplicas: 10
minReplicas: 1
maxReplicas: 50
minReplicas: 10