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

Constant increase of cpu and memory usage in our workers. #2741

Open
majamassarini opened this issue Mar 5, 2025 · 0 comments
Open

Constant increase of cpu and memory usage in our workers. #2741

majamassarini opened this issue Mar 5, 2025 · 0 comments
Labels
area/general Related to whole service, not a specific part/integration. complexity/single-task Regular task, should be done within days. kind/internal Doesn't affect users directly, may be e.g. infrastructure, DB related.

Comments

@majamassarini
Copy link
Member

The graphs show that in a week we have always a constant increase of cpu and memory usage.

Image

Image

There seem to be a strong correlation between the cpu/memory graphs and the time spent in the testing farm result handler job.

Image

Image
@nforro nforro added complexity/single-task Regular task, should be done within days. area/general Related to whole service, not a specific part/integration. kind/internal Doesn't affect users directly, may be e.g. infrastructure, DB related. labels Mar 6, 2025
@nforro nforro moved this from new to priority-backlog in Packit Kanban Board Mar 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/general Related to whole service, not a specific part/integration. complexity/single-task Regular task, should be done within days. kind/internal Doesn't affect users directly, may be e.g. infrastructure, DB related.
Projects
Packit Kanban Board
Status: priority-backlog
Milestone
No milestone
Development

No branches or pull requests
2 participants
@majamassarini @nforro