Increase Load Average after update from 2.6.32 (1.6) to 2.6.35 (1.7)

qk4l

New Member
Oct 24, 2010
15
0
1
St.Petersburg
Hi,

About five day ago I updated two servers from 2.6.32 (1.6) to 2.6.35 (1.7).

After that I noted increase of Load Average on both servers. While cpu on one (kvm3) did not change and other decreased (kvm2).

At first I decided that KSM is reason, but on one (kvm3) it do not work never (I have less than 50% RAM usage), and on other after I turfoff KSM nothing change.

I attach some files and you can see this changes.

Some body noticed increase on his/her servers?

I understand that jump LA from 0.5 to 1 may be laughing for somebody, but it`s 50% and what happens if I want add some more VE?

Thank you for attentions.

I updated kvm3 16.12 and kvm2 - 17.12.



KVM3:

~$ pveversion -v
pve-manager: 1.7-10 (pve-manager/1.7/5323)
running kernel: 2.6.35-1-pve
proxmox-ve-2.6.35: 1.6-7
pve-kernel-2.6.35-1-pve: 2.6.35-7
qemu-server: 1.1-25
pve-firmware: 1.0-9
libpve-storage-perl: 1.0-16
vncterm: 0.9-2
vzctl: 3.0.24-1pve4
vzdump: 1.2-9
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.13.0-2
ksm-control-daemon: 1.0-4

KVM2:

~$ ssh kvm2 pveversion -v
qk4l@kvm2's password:
pve-manager: 1.6-5 (pve-manager/1.6/5261)
running kernel: 2.6.35-1-pve
proxmox-ve-2.6.35: 1.6-7
pve-kernel-2.6.35-1-pve: 2.6.35-7
qemu-server: 1.1-22
pve-firmware: 1.0-9
libpve-storage-perl: 1.0-16
vncterm: 0.9-2
vzctl: 3.0.24-1pve4
vzdump: 1.2-8
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.12.5-2
ksm-control-daemon: 1.0-4

P.S. I stop two VE on kvm3 and one on kvm2 ~ 17.12.
P.S.S. I know about var. version of qemu-server but I don`t think that it`s reason.
 
Last edited:
I bet the high load comes from KSM. 2.6.35 has ksm enabled by default
Please run /etc/init.d/ksmtuned stop and then do:
echo "0 > [FONT=arial, helvetica][/FONT][FONT=arial, helvetica][/FONT]/sys/kernel/mm/ksm/run
 
@adoII Thank you for answer, but I`ve checking more than one times - KSM and ksm-control-daemon are stoped =(.

Also as I understand KSM not enable by default, It turn on by ksm-control-daemon if raw usage more than KSM_THRES_COEF or KSM_THRES_CONST.

At first I decided that KSM is reason, but on one (kvm3) it do not work never (I have less than 50% RAM usage), and on other after I turfoff KSM nothing change.