hpc:getting_started
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
hpc:getting_started [2022/10/13 13:28] – Pierre Kuenzli | hpc:getting_started [2025/06/11 12:27] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | < | + | ====== |
This document present in general what are computing clusters and what is High Performance Computing (HPC). It can be read out of curiosity, if you want to know what are those infrastructures for or if you are a potential future user with limited technical background. For more practical information on using unige HPC infrastructure, | This document present in general what are computing clusters and what is High Performance Computing (HPC). It can be read out of curiosity, if you want to know what are those infrastructures for or if you are a potential future user with limited technical background. For more practical information on using unige HPC infrastructure, | ||
Line 89: | Line 89: | ||
* Clusters are running Linux, which heavily relies on a command line interface. You will be able to perform some tasks with a graphical interface, but at some point you will have to use a command line interface. | * Clusters are running Linux, which heavily relies on a command line interface. You will be able to perform some tasks with a graphical interface, but at some point you will have to use a command line interface. | ||
* There are many users using the cluster at the same time. So you have no guarantee your computations will start immediately. | * There are many users using the cluster at the same time. So you have no guarantee your computations will start immediately. | ||
- | * You will not directly run your program on the cluster as on you do on your computer. You will ask the queueing system to run a program, and once resources are available, the queuing system will start the program. | + | * You will not directly run your program on the cluster as you do on your personnal |
* HPC clusters where not designed for interactive tasks. While doable, they are much better candidates for asynchronous computing (without user interaction). | * HPC clusters where not designed for interactive tasks. While doable, they are much better candidates for asynchronous computing (without user interaction). | ||
| | ||
- | As a user, you will interact directly with the login node only. From this computer, you will manage your file, set up your execution configuration and ask the queuing system for computation on the compute nodes. But you will never run your programs directly on the login node. | + | As a user, you will interact directly with the login node only. From this computer, you will manage your files, set up your execution configuration and ask the queuing system for computation on the compute nodes. But you will never run your programs directly on the login node. |
{{ : | {{ : | ||
Line 130: | Line 130: | ||
</ | </ | ||
- | With this file, we are telling the queuing system "I want you to run my multiply program on one processor of one of the computing node, for a maximum of one minute" | + | With this file, we are telling the queuing system "I want you to run my multiply program on one processor of one of the computing node, for a maximum |
So let's do the job. Send those files to the cluster, submit the job to the queuing system and gather results once done. | So let's do the job. Send those files to the cluster, submit the job to the queuing system and gather results once done. |
hpc/getting_started.1665667686.txt.gz · Last modified: (external edit)