High CPU Utilization

I've been noticing that Multiplicity periodically utilizes a significant amount of CPU resource on secondary after a period of time with a KVM connection.  This happens on the 'remote' machine, not the primary where I am running the KVM window, and it seems to keep one CPU core pretty well occupied (~17-25% utilization) the issue goes away after a reboot, simply disconnecting the KVM session does not cause the utilization to go down significantly (it may not hit the 25% max anymore, but generally stays above 15%).

It's possible this is starting after a period of idle time when the remote machine has turned off the screen or entered an early sleep mode - although I haven't been able to confirm this as the cause.   The issue has persisted through a full re-install of Windows 10 on the client machine after I upgraded the boot drive.

Is there any additional logging or diagnostics I can enable in Multiplicity to try to collect more info on what exactly the client might be doing?

Both machines are running Windows 10 Pro 1803 with all the latest OS updates and the latest (I believe) Multiplicity v3.44 Build 00090 (primary machine is v3.44 KVM Pro Build 00090).

Thanks for any assistance!

7,677 views 4 replies
Reply #1 Top

Hello,

I have forwarded your report to the Stardock support team for their review and recommendations.

Please keep an eye on this thread for any updates.

We really do appreciate your feedback, thanks.

AzDude
Stardock Community Assistant

Reply #2 Top

Hello,

Sorry to hear you are having trouble.

Both machines are running Windows 10 Pro 1803
End of quote

Is there a reason you are not on 1809 - the latest?

While this is entirely dependent on what the PC is sending, I am not seeing any issues with CPU usage or any increase staying persistent after taxation:

https://cdn.stardock.us/support/uploads/2019-03-13_14-29-49.mp4

----------------
Sean Drohan
Stardock Customer Service Manager

Reply #3 Top

Sorry I had 1803 in my head for some reason, they are both on 1809...

I did notice that I was able to make the offending process reset by adding the secondary via Seamless control and navigating over to it, although KVM window is the preferred connection method.

Reply #4 Top

I thought originally it was Sleep-mode related, but I'm pretty confident now that I can reproduce the problem by letting Windows turn the display off (ex. Windows power options > Screen > When plugged in, turn off after X minutes).  So it doesn't even have to go to Sleep, just turn off the display, and then when recovering the CPU utilization by MultiPLV64.EXE is very high and never backs down.

I've dropped the setting down to two minutes, and reproduced several times after clean restarts.  I can try to record a screencap tomorrow if it would help, I'm also going to try to reproduce with another client machine.

Is there any additional logging I can turn on in the product to maybe capture something more useful than a screencap?

Thanks!