Puppet using high CPU utilization in centos 7

Support
1

Hi,

We are using high end setup for our Puppet and foreman in CentOS server:
RAID5, 198GB RAM, 64 cores Processor.
But, after installation of Foreman-installer puppet is eating the CPU like
anything. We can observe CPU usage% is spiking > 4000!!!
Is it because of RAID5 processor? Can anyone help on this to resolve this
issue?

Capture.PNG663×602 6.34 KB

··· ====================================================== top - 23:18:09 up 21:17, 3 users, load average: 29.86, 21.72, 22.12 Tasks: 705 total, 1 running, 704 sleeping, 0 stopped, 0 zombie %Cpu(s): 63.2 us, 0.4 sy, 0.0 ni, 36.4 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st KiB Mem : 19778108+total, 18979132+free, 5705996 used, 2283756 buff/cache KiB Swap: 4194300 total, 4194300 free, 0 used. 19106275+avail Mem

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
36570 puppet 20 0 13.414g 2.652g 21912 S 4060 1.4 141:07.87 java
3359 sandisk 20 0 1787316 185376 45404 S 1.0 0.1 5:22.40
gnome-shell
35962 root 20 0 158272 2920 1568 R 0.7 0.0 0:06.39 top
28264 root 20 0 0 0 0 S 0.3 0.0 0:21.24
kworker/21:0
30703 root 20 0 0 0 0 S 0.3 0.0 0:14.38
kworker/26:1
32997 root 20 0 0 0 0 S 0.3 0.0 0:10.75
kworker/30:1
33369 root 20 0 0 0 0 S 0.3 0.0 0:11.32
kworker/53:2
33435 root 20 0 0 0 0 S 0.3 0.0 0:08.22
kworker/23:2
34037 root 20 0 0 0 0 S 0.3 0.0 0:09.36
kworker/35:0
34064 root 20 0 0 0 0 S 0.3 0.0 0:10.88
kworker/62:0
34461 root 20 0 0 0 0 S 0.3 0.0 0:07.47
kworker/56:2
34996 root 20 0 0 0 0 S 0.3 0.0 0:06.21
kworker/40:1
35002 root 20 0 0 0 0 S 0.3 0.0 0:06.51
kworker/51:1
35214 root 20 0 0 0 0 S 0.3 0.0 0:07.02
kworker/57:1
35966 root 20 0 0 0 0 S 0.3 0.0 0:02.58
kworker/29:1
36175 root 20 0 0 0 0 S 0.3 0.0 0:03.25
kworker/49:0
36358 root 20 0 0 0 0 S 0.3 0.0 0:01.86
kworker/39:2
36861 root 20 0 0 0 0 S 0.3 0.0 0:01.16
kworker/54:2
36890 root 20 0 0 0 0 S 0.3 0.0 0:00.84
kworker/15:1
36929 root 20 0 0 0 0 S 0.3 0.0 0:00.72
kworker/2:2
36930 root 20 0 0 0 0 S 0.3 0.0 0:01.17
kworker/59:1
36938 root 20 0 0 0 0 S 0.3 0.0 0:00.82
kworker/46:2
37013 root 20 0 0 0 0 S 0.3 0.0 0:00.76
kworker/41:0
37077 root 20 0 0 0 0 S 0.3 0.0 0:00.23
kworker/47:0
1 root 20 0 198032 11220 3972 S 0.0 0.0 0:17.96 systemd
2 root 20 0 0 0 0 S 0.0 0.0 0:00.94 kthreadd
3 root 20 0 0 0 0 S 0.0 0.0 0:00.45
ksoftirqd/0
5 root 0 -20 0 0 0 S 0.0 0.0 0:00.00
kworker/0:0H
6 root 20 0 0 0 0 S 0.0 0.0 0:04.66
kworker/u128:0
7 root 20 0 0 0 0 S 0.0 0.0 0:00.00
kworker/u129:0
8 root rt 0 0 0 0 S 0.0 0.0 0:00.45
migration/0

Best Regards,
Amrit

2

This is question rather for Puppet mailing list and not Foreman, but
generally you are doing great. Your server has 64 cores and your
long-term load is about 20, so you are utilizing it at 50%. The top
utility says that java process is utilizing about 40 cores at peaks,
which is also fine. There are likely some threads calculating
something, so top shows you that correctly.

TL;DR the box it is not swapping, so you are fine, we did a good job
setting it up via our installer!

LZ

··· On Fri, Feb 17, 2017 at 5:19 AM, Amrit Atmajit wrote: > Hi, > > We are using high end setup for our Puppet and foreman in CentOS server: > RAID5, 198GB RAM, 64 cores Processor. > But, after installation of Foreman-installer puppet is eating the CPU like > anything. We can observe CPU usage% is spiking > 4000!!!!! > Is it because of RAID5 processor? Can anyone help on this to resolve this > issue? > > ====================================================== > top - 23:18:09 up 21:17, 3 users, load average: 29.86, 21.72, 22.12 > Tasks: 705 total, 1 running, 704 sleeping, 0 stopped, 0 zombie > %Cpu(s): 63.2 us, 0.4 sy, 0.0 ni, 36.4 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 > st > KiB Mem : 19778108+total, 18979132+free, 5705996 used, 2283756 buff/cache > KiB Swap: 4194300 total, 4194300 free, 0 used. 19106275+avail Mem > > PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND > 36570 puppet 20 0 13.414g 2.652g 21912 S 4060 1.4 141:07.87 java > 3359 sandisk 20 0 1787316 185376 45404 S 1.0 0.1 5:22.40 > gnome-shell > 35962 root 20 0 158272 2920 1568 R 0.7 0.0 0:06.39 top > 28264 root 20 0 0 0 0 S 0.3 0.0 0:21.24 > kworker/21:0 > 30703 root 20 0 0 0 0 S 0.3 0.0 0:14.38 > kworker/26:1 > 32997 root 20 0 0 0 0 S 0.3 0.0 0:10.75 > kworker/30:1 > 33369 root 20 0 0 0 0 S 0.3 0.0 0:11.32 > kworker/53:2 > 33435 root 20 0 0 0 0 S 0.3 0.0 0:08.22 > kworker/23:2 > 34037 root 20 0 0 0 0 S 0.3 0.0 0:09.36 > kworker/35:0 > 34064 root 20 0 0 0 0 S 0.3 0.0 0:10.88 > kworker/62:0 > 34461 root 20 0 0 0 0 S 0.3 0.0 0:07.47 > kworker/56:2 > 34996 root 20 0 0 0 0 S 0.3 0.0 0:06.21 > kworker/40:1 > 35002 root 20 0 0 0 0 S 0.3 0.0 0:06.51 > kworker/51:1 > 35214 root 20 0 0 0 0 S 0.3 0.0 0:07.02 > kworker/57:1 > 35966 root 20 0 0 0 0 S 0.3 0.0 0:02.58 > kworker/29:1 > 36175 root 20 0 0 0 0 S 0.3 0.0 0:03.25 > kworker/49:0 > 36358 root 20 0 0 0 0 S 0.3 0.0 0:01.86 > kworker/39:2 > 36861 root 20 0 0 0 0 S 0.3 0.0 0:01.16 > kworker/54:2 > 36890 root 20 0 0 0 0 S 0.3 0.0 0:00.84 > kworker/15:1 > 36929 root 20 0 0 0 0 S 0.3 0.0 0:00.72 > kworker/2:2 > 36930 root 20 0 0 0 0 S 0.3 0.0 0:01.17 > kworker/59:1 > 36938 root 20 0 0 0 0 S 0.3 0.0 0:00.82 > kworker/46:2 > 37013 root 20 0 0 0 0 S 0.3 0.0 0:00.76 > kworker/41:0 > 37077 root 20 0 0 0 0 S 0.3 0.0 0:00.23 > kworker/47:0 > 1 root 20 0 198032 11220 3972 S 0.0 0.0 0:17.96 systemd > 2 root 20 0 0 0 0 S 0.0 0.0 0:00.94 kthreadd > 3 root 20 0 0 0 0 S 0.0 0.0 0:00.45 > ksoftirqd/0 > 5 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 > kworker/0:0H > 6 root 20 0 0 0 0 S 0.0 0.0 0:04.66 > kworker/u128:0 > 7 root 20 0 0 0 0 S 0.0 0.0 0:00.00 > kworker/u129:0 > 8 root rt 0 0 0 0 S 0.0 0.0 0:00.45 > migration/0 > ======================================================= > > Best Regards, > Amrit > > > > > > -- > You received this message because you are subscribed to the Google Groups > "Foreman users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to foreman-users+unsubscribe@googlegroups.com. > To post to this group, send email to foreman-users@googlegroups.com. > Visit this group at https://groups.google.com/group/foreman-users. > For more options, visit https://groups.google.com/d/optout.

–
Later,
Lukas @lzap Zapletal