hey Leo, you are @kohrar are you?
(https://github.com/apache/cloudstack/pull/8694)
as discussed further improvements might be desirable.
On Wed, Feb 21, 2024 at 7:36 PM Leo Leung wrote:
>
> I did some basic performance analysis on the Java process and it appears the
> high CPU usage stems from
I did some basic performance analysis on the Java process and it appears the
high CPU usage stems from the NIOSocketInputStream class which is part of the
new secure KVM VNC feature released with ACS 4.18.
In the mean time, I've sized up the Console Proxy VM compute offering with more
CPUs (1
Just a quick update:
- I see 100% CPU on the console proxy's java process if one or more VNC session
is in use, even if nothing is happening in the session (such as a blank
screen). Is this normal?
- The persistent 100% CPU appears to be triggered when I try to VNC to the
console proxy itself.
Hello everyone,
I am running CloudStack 4.18 and 4.19 in two separate environments and notice
that in both environments, the Console Proxy SystemVM is pretty much pegging
its single CPU. Logging in to the SystemVM, top reports the java process that
handles the VNC connections is constantly
