Activity
@koukibadr started using tool Jenkins , 1 week, 1 day ago.
Activity
@koukibadr started using tool Firebase , 1 week, 1 day ago.
Activity
@koukibadr started using tool Docker Compose , 1 week, 1 day ago.
Activity
@koukibadr started using tool Docker , 1 week, 1 day ago.
Activity
@koukibadr started using tool Azure Pipelines , 1 week, 1 day ago.
Activity
@koukibadr started using tool Amazon S3 , 1 week, 1 day ago.
Activity
@ravikyada started using tool Kubernetes , 1 week, 1 day ago.
Activity
@ravikyada started using tool Jenkins , 1 week, 1 day ago.
Activity
@ravikyada started using tool Grafana , 1 week, 1 day ago.
Activity
@ravikyada started using tool Docker , 1 week, 1 day ago.
At its core, Slurm uses a centralized controller (slurmctld) to track cluster state and assign work, while lightweight daemons (slurmd) on each node execute tasks and communicate hierarchically for fault tolerance. Optional components like slurmdbd and slurmrestd extend Slurm with accounting and REST APIs. A rich set of commands—such as srun, squeue, scancel, and sinfo—gives users and administrators full visibility and control.
Slurm’s modular plugin architecture supports nearly every aspect of cluster operation, including authentication, MPI integration, container runtimes, resource limits, energy accounting, topology-aware scheduling, preemption, and GPU management via Generic Resources (GRES). Nodes are organized into partitions, enabling sophisticated policies for job size, priority, fairness, oversubscription, reservation, and resource exclusivity.
Widely adopted across academia, research labs, and enterprise HPC environments, Slurm serves as the backbone for many of the world’s top supercomputers, offering a battle-tested, flexible, and highly configurable framework for large-scale distributed computing.



