Recent content by bash99

we have a mixed 4.4/5.3 cluster, it's our production system, so the upgrade is very slow. recently we got a lot problems when upgrade or add new installed 5.4 box to cluster, sometimes the whole cluster locked up, corosync use 100%cpu. only separate the new box from cluster can restore it...

It's turn out a BIOS setting problem and is sloved. The BIOS profile is setting to Performance-per-watt(DAPC), after change it to Performance-per-watt(OS), everything is ok. I guess the reason is DPAC let most cpu running in low freq, so the cfq scheduler prefer to schedule sysbench shift to...

I know it will slow because of thread contention, but not so dramatic. In a normal node: root@pve3:~# pct enter 165 [root@tmpcpu ~]# for i in 2 4 8; do sysbench --test=cpu --num-threads=$i --cpu-max-prime=10000 run | grep "total time" ; done total time: 5.1636s total time taken by event...

I've 7 node Proxmox Cluster(4.2, just wait a good time to upgrade to 4.3), and on 2 of those nodes, LXC show strange performance when run with multi-thread programs. a lxc config with 4 cpu quota root@pve2:~# more /etc/pve/lxc/165.conf arch: amd64 cpulimit: 4 cpuunits: 1024 hostname: tmpcpu...