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.

Sign up for GitHub

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

Jump to bottom

Investigate Memory Comsumption #47

Open
sbckr opened this issue Jul 11, 2023 · 0 comments
Open

Investigate Memory Comsumption #47

sbckr opened this issue Jul 11, 2023 · 0 comments
Labels
kind/bug Categorizes issue or PR as related to a bug. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@sbckr
Copy link
Member

sbckr commented Jul 11, 2023

During system tests on program executions with large input and output data, a high and rapidly increasing resource consumption could be observed in Amphora. Besides, the memory was not directly freed also with longer idle time.

The evaluation took place only superficial using kubectl top and the tool k9s. In order to exclude an impact on other services and/or the entire deployment, a more precise analysis should take place.

The following data shows the memory consumption ( and the increase) [in MB] for the up- and download of a secret with the size of 930090 bytes:

  • Upload:
    • 1968 -> 2103 (+135)
    • 2013 -> 2378 (+275)
  • Download
    • 2378 -> 3273 (+895)
    • 753 -> 2915 (+2162) (2910 after ~6m)
    • 2910 -> 3256 (+346) (3248 after ~45m)
@github-actions github-actions bot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Jul 11, 2023
@strieflin strieflin added kind/bug Categorizes issue or PR as related to a bug. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Jul 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/bug Categorizes issue or PR as related to a bug. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@strieflin @sbckr