Apache YuniKorn vs Slurm Workload Manager

Apache YuniKorn is a resource scheduler for batch, data, and machine learning workloads on Kubernetes. It is a Kubernetes-compatible alternative to the default scheduler and is described as transparent to existing Kubernetes applications. Hierarchical queues provide fine-grained tenant controls that can reflect an organization’s structure. Scheduling features include gang scheduling, FIFO and Fair job ordering, resource fairness, reservations, and preemption. A web UI centralizes cluster capacity, utilization, and application information. YuniKorn exposes metrics through Prometheus, and project guidance covers monitoring with Prometheus and Grafana. The project recommends deployment to an existing Kubernetes cluster using its Helm chart and Helm 3 or later. The software is free under the Apache License 2.0. Releases include source tarballs, which must be built before use, and prebuilt Docker images. The project advises checking release artifacts for tampering with GPG or SHA-512. Help is available through the YuniKorn Slack #yunikorn-user channel or the user mailing list.

Slurm Workload Manager is free, open-source software for allocating compute resources and scheduling work across Linux clusters. It starts and monitors jobs on allocated nodes and manages queues of pending work. Optional plugins add accounting, advanced reservations, gang and backfill scheduling, topology-aware resource selection, resource limits, and multifactor job prioritization. The system uses a central slurmctld manager and slurmd daemons on compute nodes; accounting and REST components are optional. GPU plugins support NVIDIA, AMD, Intel, AWS Trainium, and AWS Inferentia accelerators, along with NVIDIA MPS and GPU sharing. Accounting can use MySQL or MariaDB and can record data in a text file, directly in a database, or through slurmdbd for multiple clusters. Slurmrestd provides REST access, but the API is not designed for direct internet exposure and supports only unencrypted HTTP. Linux is thoroughly tested on arm64, ppc64, and x86_64; FreeBSD and NetBSD support is limited, and macOS is unsupported. Deployment is self-hosted.