Client eating up CPU

Forum / NoMachine for Windows / Client eating up CPU

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #13251
    tsorn
    Participant

    I run the NoMachine client on Windows 10, server on Linux Mint 18. The client isĀ using an enormous amount of CPU power; a constant 50 %, much more than [other products] when used in the same setup. How come? Does it have anything to do with the codec used, perhaps? Is there any way to reduce it? Client is Skylake CPU without a dedicated graphics card; Server has Nvidia GTX770 dedicated with proprietary drivers.

    Additional information added:
    NoMachine newest versions as of yesterday on both machines. The CPU consumption is consistently high during the connection (have
    tested for 2 hours). VP8 is used. Connecting to physical desktop. No VM on either machine.
    No particular software is running on the server side, but it does have 3 monitors.
    Also, disabling hardware accel on client side helped a lot. As said client has a Skylake CPU, no dedicated GPU.

    #13384
    Britgirl
    Keymaster

    You wrote that disabling hardware acceleration (decoding) on the client, the performance improves. It would seem that the HW is to blame, not really NoMachine.

    You could try using H.264 software encoding, you can follow the instructions here: https://www.nomachine.com/AR10K00706. This should help diminish the use of the CPU.

    In its current design NoMachine sends the content of all the remote monitors even though you may be viewing the content of one of the displays only client-side. This is to ensure a smoother experience in visualizing the content when you’re switching among monitors.

    This behaviour is becoming less convenient nowadays what with monitor resolutions getting larger. We are already working on improving how NoMachine handles the encoding of multi-monitors, so that each monitor is encoded separately and content is transmitted separately to the client.

    Other ways that you could further improve CPU usage is by disabling “client side image post-processing”. This applies a filter to improve the quality of the image, but consumes more CPU. This is one feature which I am sure other remote access products don’t have.

Viewing 2 posts - 1 through 2 (of 2 total)

This topic was marked as solved, you can't post.