You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
We upgrade our popeye from version 0.11.1 to 0.21.3
Previously popeye was using limits of 100 CPU and 100-200 MB Memory. with latest version it needs 500 CPU and under 1 GB of memory it gets oom killed. on some clusters it even requires 4.5GB of memory. is this something expected, or why did popeye suddenly start using so much memory.
To Reproduce
Steps to reproduce the behavior:
Upgraded popeye to latest version
Expected behavior
I would be okay with some increase, but 3-4 GB of memory requirement seems to much, when previous one used around 100-200 MB
Screenshots
Grafana output of one run
Versions (please complete the following information):
Popeye v0.21.3
K8s 1.29.7-eks
The text was updated successfully, but these errors were encountered:
Hello,
Sorry, I was on holiday and could not respond for some time.
Our clusters usually have around 10-20 nodes, and some might go up to 30 nodes.
With pods, I would say 300-600 pods.
We have different products.. each product has its cluster for the dev/prod environment.
We use following arguments:
-A -f /spinach/spinach.yaml --out html -l info --s3-bucket xyz --push-gtwy-url http://pushgateway-service:9091 --cluster xyz --kubeconfig /etc/kubeconfig/config.yaml --force-exit-zero=true
```
We tested with separating pushgateway and bucket upload into 2 separate pods as it was done previously, but it didn't lower memory useage.
Describe the bug
We upgrade our popeye from version 0.11.1 to 0.21.3
Previously popeye was using limits of 100 CPU and 100-200 MB Memory. with latest version it needs 500 CPU and under 1 GB of memory it gets oom killed. on some clusters it even requires 4.5GB of memory. is this something expected, or why did popeye suddenly start using so much memory.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I would be okay with some increase, but 3-4 GB of memory requirement seems to much, when previous one used around 100-200 MB
Screenshots
Grafana output of one run
Versions (please complete the following information):
The text was updated successfully, but these errors were encountered: