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

High CPU use after jobber test #301

Closed
samuelallan72 opened this issue May 29, 2020 · 7 comments
Closed

High CPU use after jobber test #301

samuelallan72 opened this issue May 29, 2020 · 7 comments
Assignees
Labels
Milestone

Comments

@samuelallan72
Copy link

Running jobber 1.4.3 on archlinux, built from pkgbuild.

Normal execution is fine, but when I run jobber test <any job>, cpu use of the jobberrunner for my user leaps to around 100%. i run jobber test ... again, and cpu jumps to 200%, and so on up to about 450% (this is as reported by htop; I'm assuming it's because multi cores?). Some kind of resource leak?

@D-K-E
Copy link

D-K-E commented May 31, 2020

Same issue, I downloaded debian release. jobber -v outputs Jobber 1.4.3

@dshearer
Copy link
Owner

dshearer commented May 31, 2020 via email

@MCOfficer
Copy link

MCOfficer commented Jun 1, 2020

I'm also seeing constantly high CPU load without any jobs running. Just to show off the severity, this is my netdata CPU graph:
image

  • The drop at 20:55:20 is a systemctl stop jobber
  • The short peak at 20:57:17 a systemctl start jobber
  • At 20:57:40 i jobber test a resource-intensive job (7z compression)
  • At 20:48:40 the job finished, but a certain amount of CPU load remains. Unless i restart jobber, the load will stay like this (or higher) indefinitely.

I thought that there were a lot of jobber processes, but the number was the same after a clean service start and after the test run (35).

@dshearer
Copy link
Owner

dshearer commented Jun 2, 2020

Fixed in v1.4.4. Sorry for my incompetence.

@dshearer dshearer closed this as completed Jun 2, 2020
@samuelallan72
Copy link
Author

@dshearer, thanks for the quick fix!

Sorry for my incompetence.

No not at all! Thank you for building an awesome tool. 👍 👍

@PegasisForever
Copy link

PegasisForever commented Aug 7, 2020

The docker version of jobber is not updated and still has this bug.

@MCOfficer
Copy link

You can open an issue over at https://github.com/dshearer/jobber-docker

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

No branches or pull requests

5 participants