services:cluster:start
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| services:cluster:start [2022/07/12 15:49] – [Slurm documentation] zedv | services:cluster:start [2025/02/07 16:46] (current) – fix math in table behrmj87 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Information about the HPC-Cluster ====== | ====== Information about the HPC-Cluster ====== | ||
| - | <note tip>If you have questions, you can find us on [[https:// | + | <note tip>If you have questions, you can find us on [[https:// |
| ===== Access to the Cluster ===== | ===== Access to the Cluster ===== | ||
| - | In order to get access to the department of physics HPC resources you need to send an email to hpc@physik.fu-berlin.de. Please supply the following information: | + | In order to get access to the department of physics HPC resources you need to send an email to [[hpc@physik.fu-berlin.de]]. Please supply the following information: |
| - Your ZEDAT account username | - Your ZEDAT account username | ||
| - | - The group you are using the system for (e.g. ag-netz,ag-imhof,...) | + | - The group you are using the system for (e.g. AG Netz, AG Eisert, AG Franke…) |
| - | - The software you are using for your simulations | + | - The software you are using for your numerics |
| - Software that you happen to know so well that other HPC users within the department may ask you for help. | - Software that you happen to know so well that other HPC users within the department may ask you for help. | ||
| - | - A self-contained example job that is typical for the workload you will be using the HPC systems for, ideally with a small README describing how to run it and a job script. If possible scale it so it runs between a few minutes and an hour at maximum. | + | - A self-contained example job that is typical for the workload you will be using the HPC systems for. |
| - | - If you are no longer a member of the physics department, we would like to get an estimate on how much longer you will need access to the systems (e.g. to finish some paper) | + | - If you are no longer a member of the physics department, we would like to get an estimate on how much longer you will need access to the systems (e.g. to finish some paper). |
| + | The example must contain: | ||
| + | |||
| + | - A small README | ||
| + | - a Slurm job script, and | ||
| + | - the program that is run in the example and/or all input files needed to run it, this includes data files and definitions for the environment the job is to run in (e.g. a '' | ||
| + | |||
| + | If possible: | ||
| + | |||
| + | - The example should have an option to scale it so it runs between a few minutes and an hour at maximum, so that it can be used for benchmarking. | ||
| + | |||
| + | If you can't answer the questions for your example, these steps can help you answer them | ||
| + | |||
| + | - If you have written the code yourself, what dependecies does it have (e.g. Python libraries you import)? | ||
| + | - How long does your example run? | ||
| + | - How many CPUs and how much memory does the example need? | ||
| + | - Can the example' | ||
| ===== Slurm documentation ===== | ===== Slurm documentation ===== | ||
| - | * [[important|Important notes]] on cluster | + | Read this for an introduction to Slurm queuing system, if you haven' |
| * Start with the [[slurm|Introduction to the Slurm HPC cluster]]. | * Start with the [[slurm|Introduction to the Slurm HPC cluster]]. | ||
| + | |||
| + | Read this for some important notes on the specifics of our clusters. | ||
| + | |||
| + | * [[important|Important notes]] on cluster usage | ||
| + | |||
| + | These are more specialised topics: | ||
| + | |||
| * Using [[interactivesessions|interactive sessions]] with the queuing system. | * Using [[interactivesessions|interactive sessions]] with the queuing system. | ||
| - | * How to make use of the [[gpunodes|GPU-nodes]]. | ||
| * Here is a [[nodes|list of special nodes]] that are currently not part of slurm. | * Here is a [[nodes|list of special nodes]] that are currently not part of slurm. | ||
| * Here is a [[userlist|list of HPC users]] and the software they use | * Here is a [[userlist|list of HPC users]] and the software they use | ||
| - | * Using [[sheldon-gpu|GPU nodes on sheldon]] | ||
| - | |||
| - | ===== General documentation ===== | ||
| - | |||
| - | * Robert Hübener from AG-Eisert has written a HOWTO for using [[mmacluster|Mathematica on a HPC-Cluster]]. | ||
| - | * A more current Python version has been built for cluster usage. The [[pythoncluster|Python on the HPC-Cluster]] tutorial describes how to set it up. | ||
| - | * Try to [[usetmpforio|use /tmp for I/O intensive single node jobs]] | ||
| ===== Overview of available resources ===== | ===== Overview of available resources ===== | ||
| - | The following table lists some HPC resources available at the physics department. At the end of the table we also list the resources for the ZEDAT [[http:// | + | The following table lists some HPC resources available at the physics department. The tron cluster at Takustraße |
| - | + | ||
| - | The name of the login node for each of our clusters has the same name as the cluster, e.g. the tron login node is reachable via ssh under the hostname '' | + | |
| - | ^ Hosts ^ Manager | + | The name of the login node for each of our clusters has the same name as the cluster, e.g. the sheldon login node is reachable via ssh under the hostname '' |
| - | | @# | + | |
| - | | @# | + | |
| - | | @# | + | |
| - | | @# | + | |
| - | | @#cfc:z163-z166 | SLURM | 4 | 2U | HP DL560 G8 | 4x Xeon E5-4650L | + | |
| - | | @# | + | |
| - | | | | | + | |
| - | | @#ccf:**soroban | + | ^ Hosts ^ Nodes ^ Cores/Node ^ RAM/Core ^ RAM/Node ^ CPU features ^ GPU ^ on-GPU RAM ^ #Cores ^ #RAM ^ #GPU ^ |
| - | | @#ccf:node001-002 | + | | @#cfc:** sheldon-ng |
| - | | @#ccf:node003-030 | + | | @#cfc:x[001-016, |
| - | | @#ccf:node031-100 | + | | @# |
| - | | @#ccf:node101-112 | + | | @#cfc:x[161-176] | 16 | 24 | 5.2GB | 125GB | x86-64-v3 | | | 384 | 2000GB | 0 | |
| - | | @#ccf:**#ZEDAT** | + | | @# |
| - | | | | | + | | @#cfc:xq[01-10] | 10 | 128 | 2.0GB | 250GB | x86-64-v3 | 2x A5000 | 24GB | 1280 | 2500GB | 20 | |
| - | | @#ccc:Abacus4 | + | | @# |
| + | | @#cfc:xgpu06 | 1 | 16 | 11.2GB | 179GB | x86-64-v4 | 4x nVidia RTX 2080 TI | 11GB | 16 | 179GB | 4 | | ||
| + | | @# | ||
| + | | @# | ||
| + | | @#cfc:xgpu26 | 1 | 64 | 2.0GB | 125GB | x86-64-v3 | 10x A5000 | 24GB | 64 | 125GB | 10 | | ||
| + | | @#cfc: | ||
| + | | @# | ||
| + | | @# | ||
| + | | @# | ||
| + | | @#cfc:xgpu[59-61] | ||
| + | | @# | ||
| + | | @# | ||
| - | (06.11.2018) | + | (07.02.2025) |
| {{: | {{: | ||
| {{: | {{: | ||
services/cluster/start.1657640940.txt.gz · Last modified: 2022/07/12 15:49 by zedv