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

Jenkins integration uses too much cpu #402

Closed
clofresh opened this issue Mar 11, 2013 · 9 comments
Closed

Jenkins integration uses too much cpu #402

clofresh opened this issue Mar 11, 2013 · 9 comments
Assignees
Labels
Milestone

Comments

@clofresh
Copy link
Contributor

on a 4 core machine, uses 70% of the cpu when the jenkins check is enabled, 300+ jobs, many of which keep 30-50 builds with at least 5gb of job data.

@clofresh
Copy link
Contributor Author

70% cpu as reported by the CollectorMetrics check

@remh
Copy link
Contributor

remh commented Mar 11, 2013

interesting, i'll have a look.

@remh
Copy link
Contributor

remh commented Mar 11, 2013

Confirmed on different orgs.

@randyochoa
Copy link

Hey guys, any idea what is going on with this issue? We just had our production Jenkins server crash this AM and we are trying to track down why. Wondering if dd-agent could have caused our problem.

@ghost ghost assigned LotharSee Mar 13, 2013
@LotharSee
Copy link
Contributor

I start investigating this issue.

@remh
Copy link
Contributor

remh commented Mar 16, 2013

@randyochoa
the issue has been patched and will be fixed with the next agent release.
is that good enough for you ?
we can send you the patch if needed if you can't wait for the next agent release.

thanks @LotharSee

@randyochoa
Copy link

@remh When will the next agent release be out? I think we are ok waiting.

@remh
Copy link
Contributor

remh commented Mar 18, 2013

@randyochoa we are preparing a release with this patch.
It should be out by tomorrow.

@remh
Copy link
Contributor

remh commented Mar 19, 2013

@randyochoa we are postponing a bit the release to the end of this week. Let us know in case you need a quicker fix.

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

4 participants