kohrar commented on issue #8692:
URL: https://github.com/apache/cloudstack/issues/8692#issuecomment-1962027968
I've rebuilt the cloud-systemvm files and copied it into the systemVM. I
think your change helps as the process is no longer pegging the CPU at 100%.
Now it's down to ~25% for a single connection.
```
# top -b -n 1 | head -n 15
top - 21:34:44 up 31 days, 15 min, 2 users, load average: 0.14, 0.18, 0.23
Tasks: 78 total, 2 running, 75 sleeping, 1 stopped, 0 zombie
%Cpu(s): 17.6 us, 11.8 sy, 0.0 ni, 70.6 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0
st
MiB Mem : 976.6 total, 94.3 free, 487.6 used, 394.7 buff/cache
MiB Swap: 243.0 total, 242.7 free, 0.3 used. 405.0 avail Mem
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+
COMMAND
92659 root 20 0 2880800 140376 30428 S 25.0 14.0 0:39.87 java
1 root 20 0 101588 11248 7168 S 0.0 1.1 1:00.53
systemd
2 root 20 0 0 0 0 S 0.0 0.0 0:01.18
kthreadd
3 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 rcu_gp
4 root 0 -20 0 0 0 I 0.0 0.0 0:00.00
rcu_par+
6 root 0 -20 0 0 0 I 0.0 0.0 0:00.00
kworker+
8 root 0 -20 0 0 0 I 0.0 0.0 0:00.00
mm_perc+
9 root 20 0 0 0 0 S 0.0 0.0 0:00.00
rcu_tas+
# nproc
1
```
If this is the expected CPU usage going forward, would it make sense to have
another PR that changes the default compute offerings so the console proxy VM
has more than 1 CPU by default?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
