Skip to content
Snippets Groups Projects

production/web: Align archive instance with previous instance moma

Merged Antoine R. Dumont requested to merge align-web-configuration-with-moma into staging
All threads resolved!
1 file
+ 10
6
Compare changes
  • Side-by-side
  • Inline
  • Compared to moma, it's currently undersized to 2 replicas, 2 workers, 2 threads so 8
    requests handling. As no gunicorn configuration is provided, the default values are set
    by the docker image's default values set in the Dockerfile.
    
    In moma, it was configured with 32 workers (with a timeout of 3600s). So we bump the
    number of replicas to 4, and the number of workers to 4 as well. That makes up a total
    of 32 requests that can be handled, which matches what moma used to do.
    
    This doubles the memory request since we doubled the number of workers, and current use
    is near 95% use of memory. This also aligns the request timeout to 3600s.
    
    Refs. swh/infra/sysadm-environment#5110
@@ -1149,8 +1149,17 @@ web:
deployments:
# Main instance to serve archive.softwareheritage.org
archive:
replicas: 4
gunicorn:
workers: 4
threads: 2
timeout: 3600
# autoScaling:
# minReplicaCount: 2
# maxReplicaCount: 4
# cpuPercentageUsage: 100
requestedCpu: 350m
requestedMemory: 3072Mi
requestedMemory: 6144Mi
refreshSavecodenowStatus:
enabled: true
concurrencyPolicy: Forbid
@@ -1162,11 +1171,6 @@ web:
configurationRef: postgresqlSyncmailmapsConfiguration
priorityClassName: frontend-rpc-workload
cron: "15 * * * *"
replicas: 2
# autoScaling:
# minReplicaCount: 2
# maxReplicaCount: 4
# cpuPercentageUsage: 100
hosts:
- archive.softwareheritage.org
- base.softwareheritage.org
Loading