Koordinator vs TORQUE Resource Manager

Koordinator is a free, self-hosted QoS scheduling system for Kubernetes microservices, AI, big-data, audio, and video workloads. It adds priority and quality-of-service controls so different pods and workload types can share nodes. Application profiling supports resource overcommitment while preserving QoS guarantees, and fine-grained isolation targets latency-sensitive work alongside batch jobs. Customizable policies cover Web Service, Spark, Presto, TensorFlow, and PyTorch. QoSManager tunes pod isolation using profiling, interference detection, and SLO settings. Koord-Queue supports TFJob, PyTorchJob, Spark, Argo Workflow, Ray, and native Kubernetes Jobs, with Kueue AdmissionCheck compatibility. YARN Copilot connects Hadoop YARN jobs with Kubernetes pods. Koordinator works alongside kube-scheduler, using control-plane and node components without invasive native changes. Helm 3.5 or newer and Kubernetes 1.18 or newer are required.

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.