![(please configure the [header_logo] section in trac.ini)](/ufo/chrome/site/your_project_logo.png){kind=logo}
Opened 12 years ago
Closed 12 years ago
#64 closed defect (fixed)
Jenkins always uses 300-400% of CPU
| Reported by: | Suren A. Chilingaryan | Owned by: | Matthias Vogelgesang |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Component: | Infrastructure | Version: | |
| Keywords: | Cc: | Matthias Vogelgesang |
Description
The jenkins CPU usage is always extremely high on ipepdvcompute1. It consumes 3-4 cores even if nothing is built.
Attachments (0)
Change History (4)
comment:1 Changed 12 years ago by
comment:2 Changed 12 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
1) I don't know why I am responsible for infrastructure, but ok.
2) The high load is a relatively recent thing, so I guess it must be caused by something different.
3) I updated Jenkins and fixed some problems — nothing changed.
4) I disabled the Jenkins service.
comment:3 Changed 12 years ago by
| Resolution: | fixed |
|---|---|
| Status: | closed → reopened |
You have installed Jenkins, so I thought it will be easier for you to find the problem. Anyway, it looks like a kernel bug: http://marc.info/?l=linux-kernel&m=134113389621450&w=2
Quick fix to call the following line in boot.local:
date -s "`date`"
Please, can you check that everything fine with jenkins and re-enable if so?
comment:4 Changed 12 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | reopened → closed |
Yes, everything runs and builds as smooth as before.
Actually, it is even higher, up-to 600%. There is a lot of ksoftirqd/* processes activated when jenkins is running.