Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

chore: update memory and cpu limits #444

Merged
merged 1 commit into from
Jul 21, 2022
Merged

chore: update memory and cpu limits #444

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
28 changes: 12 additions & 16 deletions devops/dev/values.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -126,24 +126,20 @@ iam-cache-server-helm:
DB_MAXIMUM_CONNECTION_POOL: 56 # https://github.com/energywebfoundation/iam-cache-server/blob/develop/README.md#connection-pooling
SENTRY_ENV: dev

resources: { }
# We usually recommend not to specify default resources and to leave this as a conscious
# choice for the user. This also increases chances charts run on environments with little
# resources, such as Minikube. If you do want to specify resources, uncomment the following
# lines, adjust them as necessary, and remove the curly braces after 'resources:'.
# limits:
# cpu: 100m
# memory: 128Mi
# requests:
# cpu: 100m
# memory: 128Mi
resources:
limits:
cpu: 750m
memory: 768Mi # spike of memory on initilaization of didkit-wasm-node requires higher limit https://github.com/spruceid/didkit/issues/301
requests:
cpu: 500m
memory: 256Mi

autoscaling:
enabled: false
minReplicas: 1
maxReplicas: 1
targetCPUUtilizationPercentage: 80
# targetMemoryUtilizationPercentage: 80
enabled: true
minReplicas: 2
maxReplicas: 4
targetCPUUtilizationPercentage: 60
targetMemoryUtilizationPercentage: 85

nodeSelector: { }

Expand Down
4 changes: 2 additions & 2 deletions devops/prod/values.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -131,7 +131,7 @@ iam-cache-server-helm:
resources:
limits:
cpu: 750m
memory: 384Mi
memory: 768Mi # spike of memory on initilaization of didkit-wasm-node requires higher limit https://github.com/spruceid/didkit/issues/301
requests:
cpu: 500m
memory: 256Mi
Expand All @@ -140,7 +140,7 @@ iam-cache-server-helm:
enabled: true
minReplicas: 3
maxReplicas: 6
targetCPUUtilizationPercentage: 50
targetCPUUtilizationPercentage: 60
targetMemoryUtilizationPercentage: 85

nodeSelector: { }
Expand Down
8 changes: 4 additions & 4 deletions devops/staging/values.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -133,17 +133,17 @@ iam-cache-server-helm:

resources:
limits:
cpu: 500m
memory: 384Mi
cpu: 750m
memory: 768Mi # spike of memory on initilaization of didkit-wasm-node requires higher limit https://github.com/spruceid/didkit/issues/301
requests:
cpu: 250m
cpu: 500m
memory: 256Mi

autoscaling:
enabled: true
minReplicas: 2
maxReplicas: 4
targetCPUUtilizationPercentage: 50
targetCPUUtilizationPercentage: 60
targetMemoryUtilizationPercentage: 85

nodeSelector: { }
Expand Down