School of Computer Science Wiki

The current Linux/NoMachine setup has two main issues. An increase in VSCode sessions has increased the total resource consumption on the linux nodes.

Any solution other than rebuilding the current system as is will involved parallelizing the setup to reduce the impact any one failed node will have on other students using the cluster.

Most potential solutions suggest breaking apart the NoMachine and SSH services as it is easier (and cheaper) to parallelize the SSH systems where as NoMachine is licenses per server and CPU core.

Per user memory and cpu limits can be enforced using cgroups/systemd.

• Easier to setup
• Fewer nodes to manage
• Should keep one user from taking down entire cluster

• Does not limit impact by any one node becoming unavailable