Overcommitting of Coefficients

This capability is exclusive to DaDesktop Private Server (DDPS) and DaDesktop On-Premise (DDOP) environments.

 

As courses grow more complex and demand greater processing power—especially when dealing with nested virtualization or higher performance needs for many trainee desktops—you might occasionally encounter an error like this:

Over Committed warning message

This warning appears for CPU, memory, or disk space issues. Your first step should be to relocate your machines to a less loaded server or data center in Poland, or reduce resource demands whenever possible.

If neither option is feasible, and you’re just slightly exceeding the usual unit limits, you can apply a temporary fix by 'over-committing' one or more of the CPU, memory, or disk coefficients. This can be done through the GUI as shown below.

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

Over-commit CPU Co-efficient

The server list also indicates which servers are currently using over-committed coefficients. This comes in handy after a course wraps up, when you’ll want to revert coefficients to their defaults.

ggdfgdf

 

 

 

 

 

 

 

 

 

 

Think of any adjustments as a temporary workaround, not a permanent fix for resource shortages. Always revert any changes made to allow a course to proceed once the course is finished.
 

DaDesktop On-premise Requirements

The over-committing capability relies on tpapi, a component of the DaDesktop codebase. At present, tpapi works only with Python 3.12, which means the operating system must be at least Ubuntu 23.10.