Skip to content
SPECIFICTION
Get listed

NVIDIA Base Command Manager vs TORQUE Resource Manager

NVIDIA Base Command Manager

nvidia.com

TORQUE Resource Manager

github.com

Side by side

FigureNVIDIA Base Command ManagerTORQUE Resource Manager
Price fromFreeFree
Free planYesYes
Free trial——
Open source——
WebYes—
macOS—Yes
LinuxYesYes
API—Yes
Self-hosted—Yes
Plans published41
Spec score · GPU Cluster Management Software6.5 (#17)7.5 (#12)

Plans

NVIDIA Base Command Manager

  • Free-to-use Base Command ManagerFree
  • Base Command Manager with standalone supportPriced on request
  • NVIDIA AI EnterprisePriced on request
  • NVIDIA Mission ControlPriced on request

NVIDIA Base Command Manager pricing →

TORQUE Resource Manager

  • TORQUE Resource ManagerFree

TORQUE Resource Manager pricing →

In their own words

NVIDIA Base Command Manager

NVIDIA Base Command Manager provides Linux and web tools for deploying and administering compute environments. It supports OS image deployment, PXE bootstrapping, lifecycle management, hardware inventory, API access, and out-of-band management. The Free-to-use Base Command Manager plan costs nothing and allows 8 accelerators per server, node, or system, with no limit on the number of servers, nodes, or systems. A standalone-support option combines the manager license with NVIDIA Enterprise Support. NVIDIA AI Enterprise adds GPU Operator, Network Operator, vGPU, and AI and data-science software. NVIDIA Mission Control includes Run:ai, UFM, NetQ, and additional Mission Control capabilities. The product therefore offers a no-cost base tier alongside options that add support or broader NVIDIA management and software capabilities.

Visit nvidia.com

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.

Visit github.com