High RAM usage

[Steve92]

Hello,

I’ve noticed a high RAM usage on ECS server : about 1 GB per connected user !

It seems high for a “routing device”.

I guess it’s more than a “routing device” …

Please could you explain me this high RAM usage ?

Thanks,

Regards,

Steve.

[Steve92]

Hi!

Is this article still OK for v8 ?

NoMachine – Guidelines For Sizing A NoMachine Cloud Server Multi Server Setup And Benchmark Tests For V. 6 And V. 7 – Knowledge Base

 

Steve.

[Britgirl]

No, it includes data based on earlier versions. Better for version is the following document for NoMachine products in general https://kb.nomachine.com/AR02P00966. We will be adding more documentation soon about version 8 and the upcoming version 9.

That said, 1 GB per user is certainly not right. Please show us the list of processes showing such high CPU usage. Also, logs from the ECS server host, also knowing what OS version it is would be useful as well.

[Steve92]

Thanks for this more recent link but alas it doesn’t deal with ECS sizing.

 

[Britgirl]

Please show us the list of processes showing such high CPU usage. Also, logs from the ECS server host, also knowing what OS version it is would be useful as well.

[Steve92]

Hi,

After reboot RAM usage is much more reasonable.

But I’d like advice to size the RAM.

How much RAM is needed on ECS for:

– 10 concurent users ?
– 20 concurrent users ?
– 50 concurrent users ?

From what number a cluster is advised ?

Thanks,

Regards,

Steve.

[fisherman]

Hi,

I just compared my installation with the mentioned article, and here are some general RAM requirements based on my test now on Ubuntu 22.04 where I used an example from the mentioned article :

Base RAM Usage of NoMachine processes:

• 170 MB – Base installation
• 17 MB per child server – To monitor availability
• 20 MB per connected user per node

Additional RAM for NoMachine WebPlayer when using a Web browser to connect to the server:

• 54 MB per session

Examples of RAM Usage:
Scenario 1: 10 nodes 5 concurrent users

• NoMachine Player: 170MB (base) + 170MB (connected nodes) + 100MB (connections) = 440MB RAM
• NoMachine WebPlayer:  170MB (base) + 170MB (connected nodes) + 100MB (connections) + 270MB (web) = 710MB RAM

Scenario 2: 500 nodes, 50 concurrent users

• NoMachine Player: 170MB (base) + 8.5GB (connected nodes) + 1GB (connections) = 9.67GB RAM
• NoMachine WebPlayer: 170MB (base) + 8.5GB (connected nodes) + 1GB (connections) + 2.7GB (web) = 12.37GB RAM

On version 8, NoMachine has a high-availability cluster.
– Master cluster peer that accepts incoming connections
– Slave cluster that remains in synchronization mode and takes over automatically if the Master Node goes down.

This ensures failover protection and reduces downtime in critical environments.

[Author]

Posts