Description Henrik Andersson 2016-08-26 09:30:25 CEST

Sometimes it is desirable to limit the amount of sessions per agent. One reason being that a ThinLinc cluster provides CPU/GPU/Memory resources to the end-users and a session is "guaranteed" to get a slice of the resources on the agent. 

Lets say we have this CAD application with the CPU/GPU/Memory constraints. Application needs at least 2 cores and 8Gb memory. The application needs at least 1/8 of GPU (VirtualGL) to work smoothly. As the 1/8 GPU constraints we only can place 8 sessions on one agent and the server needs to have at least 8*2 CPU cores and 8*8Gb memory.

Suggestions is to add a /vsmagent/session_limit configuration variable with default value of 0 which means unlimited. When limit is set and reached, the agent is not used in loadbalancer.