If the standard deployment size is insufficient for concurrent execution, create a larger deployment. To do so, increase the number of platform nodes and, accordingly, the resource requests and limits for the platform services.
Consider the following resource sizing recommendation as a base recommendation. You might need to change resources relative to the recommendation. It is critical to pair this sizing with what you observe in monitoring and make other adjustments accordingly.
Domino recommends that you consult your Customer Success Manager for customizations and advice before you deploy this model.
- Number of platform nodes
-
6
- CPU per node
-
8 cores
- Memory per node
-
32 GB
- Maximum concurrent executions
-
600
If you use this sizing model, ensure that your platform node pool can scale up to the number of platform nodes shown above. Merge the following resource request and limit overrides to the fleetcommand-agent configuration file to apply them and then run the installer.
Important
|
It is critical to preserve values by running the installer. Applying ad hoc |
release_overrides:
cluster-autoscaler:
chart_values:
resources:
limits:
cpu: 1
memory: 2Gi
requests:
cpu: 50m
memory: 100Mi
data-plane:
chart_values:
agent:
deployment:
resources:
limits:
cpu: 4000m
memory: 4Gi
requests:
cpu: 2000m
memory: 2Gi
elasticsearch:
chart_values:
esJavaOpts: '-Xms8g -Xmx8g'
replicas: 5
resources:
requests:
cpu: 1
memory: 8Gi
git:
chart_values:
persistence:
size: 160Gi
resources:
limits:
cpu: 4
memory: 4Gi
requests:
cpu: 2
memory: 2Gi
image-cache-api:
chart_values:
resources:
limits:
cpu: 2
memory: 2Gi
requests:
cpu: 2
memory: 2Gi
mongodb-replicaset:
chart_values:
persistentVolume:
size: 120Gi
resources:
requests:
cpu: 2
memory: "4Gi"
newrelic-infrastructure:
chart_values:
resources:
limits:
memory: 2Gi
requests:
cpu: 50m
memory: 30Mi
newrelic-logging:
chart_values:
resources:
limits:
cpu: 1
memory: 600Mi
newrelic-open-metrics:
chart_values:
resources:
limits:
cpu: 1200m
memory: 2Gi
requests:
cpu: 200m
memory: 512Mi
nucleus:
chart_values:
config:
javaMaxHeap: 6G
keycloak: {}
replicaCount:
frontend: 3
resources:
dispatcher:
limits:
cpu: 5
memory: 11Gi
requests:
cpu: 4
memory: 8Gi
frontend:
limits:
cpu: 5
memory: 11Gi
requests:
cpu: 4
memory: 8Gi
prometheus:
chart_values:
server:
resources:
limits:
memory: 14Gi
requests:
cpu: 1100m
memory: 7Gi
prometheus-adapter:
chart_values:
resources:
limits:
cpu: 600m
memory: 512Mi
requests:
cpu: 250m
memory: 256Mi
rabbitmq-ha:
chart_values:
resources:
limits:
cpu: 2
memory: 4Gi
requests:
cpu: 1
memory: 2Gi
To check the status of your available platform resources and allocation, run the following:
kubectl describe nodes -l dominodatalab.com/node-pool=platform | grep -A 10 Allocated