In 10.0.4.0 and greater, you can optionally override the CPU and Memory resources used
by postgres database components.
About this task
There are three postgres components:
postgres
pgBouncer
pgBackRest
The default resources used in postgres
pgBouncer
and
pgBackRest
components are:
Table 1. Postgres component default resources
Resource |
Postgres DB |
pgBouncer |
pgBackRest |
Memory Request |
512Mi |
24Mi |
48Mi |
Memory Limit |
8Gi |
128Mi |
128Mi |
CPU Request |
600m |
80m |
80m |
CPU Limit |
1500m |
200m |
200m |
Procedure
To override resources, complete the following procedure
-
Create an extra-values yaml file, or add values to an existing extra-values file.
Examples:
- Example yaml, to replace all
postgres
resources:spec:
template:
- name: mgmt-pgcluster
containers:
- name: postgres
resources:
requests:
cpu: 1500m
memory: 8Gi
limits:
cpu: 600m
memory: 512Mi
- Example yaml, to replace all
pgBouncer
resources:spec:
template:
- name: mgmt-pgcluster
containers:
- name: pgBouncer
resources:
requests:
cpu: 200m
memory: 128Mi
limits:
cpu: 300m
memory: 256Mi
- Example yaml,to replace CPU limit of
postgres
database:spec:
template:
- name: mgmt-pgcluster
containers:
- name: postgres
resources:
limits:
cpu: 1000m
- Example yaml, to replace CPU limits of
postgres
database and
pgBouncer
:spec:
template:
- name: mgmt-pgcluster
containers:
- name: postgres
resources:
limits:
cpu: 1000m
- name: pgBouncer
resources:
limits:
cpu: 1000m
- Set the extra values file:
apicup subsys set <SUBSYSTEM_NAME> extra-values-file=<PATH_TO_EXTRA_VALUES_FILE>
- Apply the overrides:
apicup subsys install <SUBSYSTEM_NAME>
- Check health of cluster:
apicup subsys health-check <SUBSYSTEM_NAME>
Results
The postgres components will restart with updated values.