============== Clusters usage ============== .. note:: See `our news feed `_ for regular updates A mandatory prerequisite for running computational tasks on PSMN is to request computing resources. This is done via a job scheduler (or resource scheduler, or batch manager), whose very purpose is to match computing resources in the cluster (CPUs, memory, ...) with user resource requests. The scheduler provides three key functions: #. it allocates access to resources (compute nodes) to users for some duration of time so they can perform work, #. it provides a framework for starting, executing, and monitoring work (typically a parallel job such as MPI) on a set of allocated nodes, #. it arbitrates contention for resources by managing a queue of pending jobs. :term:`PSMN` is using `Slurm `_, an open-source resource manager and job scheduler. We specificaly use `v20.11 `_ of :term:`Slurm`. For those familiar with GridEngine, Slurm documentation provide a `Rosetta Stone for schedulers `_, to ease the transition. :term:`Slurm` supports a variety of job submission techniques. By accurately requesting the resources you need, you will be able to get your work done. PSMN synoptic, for reference: .. figure:: /_static/PSMN_network_synoptic_a3_2022d.png :alt: PSMN network synoptic 2022 :width: 660px :align: center PSMN network synoptic (as of 2022) .. toctree:: :maxdepth: 1 login_nodes submitting priority preemption batch_scripts interactive computing_resources accounting connecting_to_nodes partitions_overview .. figure:: /_static/partitions_2023a.png :alt: PSMN clusters 2023 :width: 400px :align: center A quick view of PSMN clusters