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

Linear growth of the memory consumption #1714

Open
Tomasz-Smelcerz-SAP opened this issue Jul 25, 2024 · 1 comment
Open

Linear growth of the memory consumption #1714

Tomasz-Smelcerz-SAP opened this issue Jul 25, 2024 · 1 comment
Labels
area/performance Related to all activities around Kyma performance, scalability, and resource utilization kind/bug Categorizes issue or PR as related to a bug.

Comments

@Tomasz-Smelcerz-SAP
Copy link
Member

Tomasz-Smelcerz-SAP commented Jul 25, 2024

Description

The LM Pod memory consumption grows linearly. This may indicate a memory "leak" or some ever-growing cache.
Requires investigation

Timebox: 3 days

Steps to reproduce

  • Take a look at the collected LM memory usage metrics

Environment Type

Managed

Environment Info

Kubernetes Version: x.y.z
Docker Version: x.y.z
Kyma CLI Version: x.y.z
If used - k3d/k3s/minikube versions

Attachments

The "Drops" in the graph are related to the new LM instance (version update or redeployment). It's not GC-related memory release. Every color is a different LM instance.

image

@Tomasz-Smelcerz-SAP Tomasz-Smelcerz-SAP added kind/bug Categorizes issue or PR as related to a bug. area/performance Related to all activities around Kyma performance, scalability, and resource utilization labels Jul 25, 2024
@janmedrek
Copy link
Contributor

pprof tool is available, there are some dumps present that we could use.

Image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/performance Related to all activities around Kyma performance, scalability, and resource utilization kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

No branches or pull requests

2 participants