Code module: Scaling

Scaling is based on CodeInstance parameter scaling.targetUsercount — according to its value, module changes HPA, PDB, CPU and memory requests/limits

Warning! Any “burstable” instance types in cloud infrastructure are not recommended due to inconsistent performance.

The scaling.targetUserCount parameter supports a value of 10; however, this is intended exclusively for internal use by developers Use of this value in any other environments is not recommended and may lead to system instability or unexpected behavior.

Architecture reference

Resource capacity table

All calculations are made based on scaling.targetUserCount parameter

Given table represents resources needed for single replicas of each component. For HA mode consider at least twice more capacity

Optional components are marked with * The first line in each cell stands for kubernetes requests, the second - for limits

Autoscaling

Almost all components support horizontal autoscaling when HA-mode is enabled. All components have at least 2 replicas. Maximum replicas described in table below:

Optional components are marked with *

Tuning Git storage

If you see a non-empty ‘OOM events’ table in Grafana or a firing GitalyCgroupMemoryOOM alert in Prometheus, you likely need to adjust the memory and CPU resources for Gitaly. Increase the spec.gitData.resources in your configuration ( e.g., set memory to 16Gi and CPU to 4). After updating, apply the changes and monitor Gitaly for improvements.

When scaling Git storage, the following parameter precedence must be observed:

1. spec.gitData.resources
2. spec.scaling.targetUserCount

Example 1:

`spec.gitData.resources.cpu`: 1  
`spec.gitData.resources.memory`: 1Gi  
`spec.scaling.targetUserCount`: 3000

Based on the resource table described above, we would expect:

• memory: 4Gi
• cpu: 2

However, due to parameter precedence, the actual result will be:

• memory: 1Gi
• cpu: 1

💡 Note: When a parameter is explicitly set in spec.gitData.resources, it always takes precedence over the automatic calculation.

Example 2:

`spec.gitData.resources.cpu`: 5  
`spec.gitData.resources.memory`: ***intentionally omitted***  
`spec.scaling.targetUserCount`: 3000

Based on the resource table described above, we would expect:

• memory: 4Gi
• cpu: 2

However, because of parameter precedence—and since spec.gitData.resources.memory was not specified—the actual result will be:

• memory: 4Gi (from the scaling table)
• cpu: 5 (from spec.gitData.resources.cpu)

💡 Important: If any resource (CPU or memory) is not specified in spec.gitData.resources, the value from the scaling table is applied.