NVIDIA Mission Control vs TORQUE Resource Manager
NVIDIA Mission Control
nvidia.comTORQUE Resource Manager
github.comSide by side
| Figure | NVIDIA Mission Control | TORQUE Resource Manager |
|---|---|---|
| Price from | — | Free |
| Free plan | — | Yes |
| Free trial | — | — |
| Open source | — | — |
| Web | Yes | — |
| macOS | — | Yes |
| Linux | Yes | Yes |
| API | — | Yes |
| Self-hosted | Yes | Yes |
| Plans published | 1 | 1 |
| Spec score · GPU Cluster Management Software | 7.2 (#15) | 7.5 (#12) |
| Purpose | NVIDIA Mission Control is an integrated AI factory management platform for enterprise AI infrastructure that combines cluster automation and operational best practices in one control plane. | TORQUE is an open-source resource manager and queue manager based on the original PBS resource manager. |
| Support | NVIDIA directs Mission Control customers to NVIDIA Enterprise Support Services for expert support and guidance. | The project README directs questions and contributions to the [email protected] mailing list. |
Plans
In their own words
NVIDIA Mission Control
NVIDIA Mission Control has no write-up on Specifiction yet; its figures are above.
TORQUE Resource Manager
TORQUE Resource Manager is an open-source resource and queue manager for compute clusters, based on the original PBS resource manager. The project is free, with Linux, macOS, API and self-hosted options. TORQUE 4.0 release notes state that it can support clusters with more than 15,000 compute nodes; that release also introduced a multithreaded pbs_server intended to improve command response and job throughput. An optional MOM hierarchy can reduce update traffic from compute nodes to pbs_server and lets administrators manage network communication. In version 4.0, component communication moved to TCP/IP, removing UDP and RPP. The trqauthd daemon authorizes client connections to pbs_server and must run as root on client hosts. Linux builds can optionally use control groups and cpusets, and documentation describes integration with Moab Workload Manager. The project is built from source using configure and make; installation instructions also cover RPM and self-extracting package creation. Its license terms are in the repository's PBS_License.txt. A compatibility caveat for version 4.0 is that its components cannot communicate with earlier TORQUE versions, so rolling upgrades will not work.