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
{{ message }}
This repository has been archived by the owner on Jul 11, 2023. It is now read-only.
We did a scalability tests on cf-for-k8s version v-0.6.0. We deployed 1000 apps out of which 50 apps are meant to crash frequently. We could see eirini-events pod was consuming high memory > 10Gi and automatically restart happens and memory reduces. We suspect some memory leak.
Steps to reproduce
Deploy crashing apps - Example and observe the eirini-events pod memory usage.
What actually happened
Memory consumption is very high
The text was updated successfully, but these errors were encountered:
We're having a problem reproducing this. We're not seeing any significant memory increases with 400 happy apps, and 50 crashing apps. If you could give us some steps to reproduce the environment you're seeing this in that would be good.
Also though, we have totally rewritten the event reporter code since the version included in cf-for-k8s v0.6.0. It might be worth repeating the experiment with the next cf-for-k8s, as it could well be already fixed.
Description
We did a scalability tests on cf-for-k8s version v-0.6.0. We deployed 1000 apps out of which 50 apps are meant to crash frequently. We could see
![image](https://user-images.githubusercontent.com/29627753/92374408-4ad46300-f11d-11ea-8439-1f140ab5f084.png)
eirini-events
pod was consuming high memory > 10Gi and automatically restart happens and memory reduces. We suspect some memory leak.Steps to reproduce
Deploy crashing apps - Example and observe the eirini-events pod memory usage.
What actually happened
Memory consumption is very high
The text was updated successfully, but these errors were encountered: