Backend.AI vs TORQUE Resource Manager

Backend.AI is an AI infrastructure platform for building, training, and serving models, as well as running parallel computing jobs. Its container-level GPU virtualization divides physical GPU capacity into fractional allocations so multiple users can share a GPU. The Sokovan scheduler supports multi-node, multi-tenant workloads and policy-based resource management. The platform says its hardware abstraction layer supports more than 12 accelerator types, including products from NVIDIA, AMD, Intel, Rebellions, and FuriosaAI. It can be deployed on-premises, in public clouds, or in a hybrid setup; installation, model deployment, and updates can operate without internet connectivity in air-gapped networks. The browser-based WebUI provides cluster management, resource and session monitoring, and policy-based allocation. Listed cloud environments include AWS, GCP, Azure, and OCI. Storage integrations include VAST, WEKA, Pure Storage, and IBM Storage Scale, with NVIDIA GPUDirect Storage support. Open-source is free for home users installing on their own hardware. Enterprise plans require a quote. Production guidance says compute nodes should be network-isolated with restricted inbound access.

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.