Over-committing Coefficients

This capability is exclusively offered on: DaDesktop Private Server (DDPS) and DaDesktop On-Premise (DDOP).

 

As courses grow more complex and demand greater processing power—especially when using nested virtualisation or supporting a large number of trainee desktops—you may occasionally see an error message like this :-

The warning typically relates to CPU, memory, or disk space. Your first step should be to move the affected machine(s) to a less loaded server or data centre, or to scale back the resource demands if you can.

If you can’t do either, and your running units only slightly exceed the usual maximum, a quick workaround is to temporarily enable 'over-committing' for one or more of the CPU, memory, or disk coefficients. You can do this through the GUI, as shown here.

Navigate to /da/admin/servers/all, click the Edit button for your server, and scroll down to the relevant section.

The server list also indicates which servers are using over-committed coefficients. This comes in handy when you want to clear these after a course ends and return to the default settings.

 

 

 

 

 

 

 

 

 

 

 

Any changes you make should be seen as a temporary fix and not a permanent solution for resource shortages. Revert them after the course concludes.
 

DaDesktop On-premise Requirements

The over-committing function relies on tpapi, a component of DaDesktop codebase. Currently, tpapi only works with Python 3.12, so the OS must be at least Ubuntu 23.10.