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.

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

Check Optimize resource limits/requests #298

Closed
Zelldon opened this issue Apr 26, 2022 · 2 comments · Fixed by #300
Closed

Check Optimize resource limits/requests #298

Zelldon opened this issue Apr 26, 2022 · 2 comments · Fixed by #300
Assignees

Comments

@Zelldon
Copy link
Member

Zelldon commented Apr 26, 2022

Check whether we use the same resource limits as in SaaS, this is what we agreed on

related to #126

@Zelldon Zelldon added the task label Apr 26, 2022
@Zelldon Zelldon self-assigned this Apr 26, 2022
@Zelldon
Copy link
Member Author

Zelldon commented Apr 27, 2022

SaaS G3-S

Limit Request
Importer Replicas 1
Importer CPU 1 0.3
Import Memory 1 0.4
Webapp replicas 2  
Webapp CPU 1 0.3
Webapp Memory 1 0.4

Our current defaults in helm charts

# Resources configuration to set request and limit configuration for the container https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/#requests-and-limits
  resources:
    requests:
      cpu: 400m
      memory: 1Gi
    limits:
      cpu: 1000m
      memory: 2Gi

@Zelldon
Copy link
Member Author

Zelldon commented Apr 27, 2022

I guess i would go with the same as operate currently uses, which is a kind of importer and webapp resources combined. Makes sense since we have just on deployment for now.

# Resources configuration to set request and limit configuration for the container https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/#requests-and-limits
  resources:
    requests:
      cpu: 600m
      memory: 1Gi
    limits:
      cpu: 2000m
      memory: 2Gi

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant