With Windows Server 2008, it was possible to use Windows System Resource Manager’s ( WSRM ) Equal_Per_Session policy to control CPU allocation of sessions. This ensured that no session would hog CPU and affect the performance of other sessions on that server so that all sessions on a TS Server would get an equal share of CPU. However, in Windows 2008 it could take up to several seconds before a runaway process was throttled, meaning that users would be adversely impacted until this throttling occurred.
In Windows Server 2008 R2 Remote Desktop Services, we have added kernel-based dynamic fair share scheduling (DFSS) to control CPU allocation. This system is able to throttle runaway processes in a matter of milliseconds, ensuring that the impact of runaway processes on users is immediately minimized.
By default DFSS gives equal weights to all sessions, i.e. all sessions are given equal share of CPU.
But what if an administrator wants to give different CPU shares to different user sessions
For example, assume an RD Server running 50 sessions and every session is taking 2% of CPU (i.e. total CPU usage on the server is 100%) and the administrator wants to do some important maintenance work at that time. Because of the heavy load on the server, the admin will end up spending more time in doing this. This can be avoided if administrators are assigned Premium priority in WSRM’s “Weighted_Remote_Sessions” policy. Other scenarios can be: in an organization executives are given higher priority over other workers, or the Sales department has higher priority over the Manufacturing department, etc.
The administrator can allocate different CPU shares to different sessions using WSRM (Windows System Resource Manager). WSRM is an optional server feature used for managing system resource (processor and memory) usage. This feature has been part of the operating system since Windows Server 2008.
WSRM has a new built-in policy called “Weighted_Remote_Sessions”. This policy allows an administrator to categorize users into one of three priority groups: premium , standard and basic . WSRM ensures that users belonging to the premium group will get more CPU resources than those in standard, who will in turn get more CPU resources than users in basic.
You can use this feature by following the steps below.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.