Skip to content
This repository has been archived by the owner on Feb 14, 2023. It is now read-only.

Log Cache should allow operators to set a fixed memory limit #36

Closed
KesavanKing opened this issue Sep 8, 2020 · 2 comments
Closed

Log Cache should allow operators to set a fixed memory limit #36

KesavanKing opened this issue Sep 8, 2020 · 2 comments

Comments

@KesavanKing
Copy link

We did a scalability tests on cf-for-k8s version 0.6.0. We were succeeded in deploying 1600 apps. To simulate real workload scenario we deploy apps which generate 1 log/sec and 1 req/sec. During the tests we could observe log-cache consumes > 10Gi of memory . We tried by scaling to two replicas, even with that it memory spikes up.

Below graph show you the number of apps deployed vs log-cache memory.

image

Just a note: Fluentd was consuming an average of 2.5Gi

@cf-gitbot
Copy link
Collaborator

We have created an issue in Pivotal Tracker to manage this. Unfortunately, the Pivotal Tracker project is private so you may be unable to view the contents of the story.

The labels on this github issue will be updated when the story is started.

@pianohacker
Copy link
Contributor

This should be fixed in version 0.5.0.

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

No branches or pull requests

3 participants