-
Notifications
You must be signed in to change notification settings - Fork 812
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
Comments
70% cpu as reported by the CollectorMetrics check |
interesting, i'll have a look. |
Confirmed on different orgs. |
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. |
I start investigating this issue. |
@randyochoa thanks @LotharSee |
@remh When will the next agent release be out? I think we are ok waiting. |
@randyochoa we are preparing a release with this patch. |
@randyochoa we are postponing a bit the release to the end of this week. Let us know in case you need a quicker fix. |
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.
The text was updated successfully, but these errors were encountered: