Difference between revisions of "Getting Started"
| Line 35: | Line 35: | ||
* memory resources (how much RAM/storage) | * memory resources (how much RAM/storage) | ||
* how to actually execute your application | * how to actually execute your application | ||
| + | which obviously has to fit within the boundaries of the running system. If you ask for more than there is, chances are, the scheduler will take this job and wait until you buy and still the missing hardware -> forever. Information over the available hardware can be found in the following table. | ||
This ususally is done with a [[Jobscript]]. When you have this jobscript ready with the help of [[jobscript-examples]], colleagues or the [[Support]], you can submit it to the respective [[Scheduler]]. | This ususally is done with a [[Jobscript]]. When you have this jobscript ready with the help of [[jobscript-examples]], colleagues or the [[Support]], you can submit it to the respective [[Scheduler]]. | ||
{| class="wikitable" style="width: 40%;" | {| class="wikitable" style="width: 40%;" | ||
| − | | IT Center - RWTH Aachen | + | | IT Center - RWTH Aachen [https://doc.itc.rwth-aachen.de/display/CC/Hardware+of+the+RWTH+Compute+Cluster] |
| − | | RRZE - Erlangen | + | | RRZE - Erlangen [https://www.anleitungen.rrze.fau.de/hpc/] |
| − | | ZIH - Dresden | + | | ZIH - Dresden [https://doc.zih.tu-dresden.de/hpc-wiki/bin/view/Compendium/HardwareTaurus] |
|- | |- | ||
| [[LSF]] | | [[LSF]] | ||
| Line 46: | Line 47: | ||
|} | |} | ||
| − | After this the application is executed when a set of nodes (computers) are allocated the your 'job' by the scheduler. Usually there is (optionally) Email notification on start/finish of jobs. | + | After this the application is executed when a set of nodes (computers) are allocated the your 'job' by the scheduler. Usually there is (optionally) Email notification on start/finish of jobs. If the specified time runs out, before your application finishes and exits, it will be terminated. |
== Modules or How-To-Use-Software-Without-installing-everything-yourself == | == Modules or How-To-Use-Software-Without-installing-everything-yourself == | ||
| − | A lot of applications rely on 3rd party software. | + | A lot of applications rely on 3rd party software. One prominent example beeing compilers, this software is usually loadable with the module system. Depending on the |
Revision as of 16:42, 20 December 2017
Access
Depending on the specific supercomputer, one has either has to register to get a user account or write a project proposal and apply for computing resources that way. The respective pages are linked in this overview:
| IT Center - RWTH Aachen [1] | RRZE - FAU Erlangen [2] | ZIH - TU Dresden [3] |
after this is done and login credentials are supplied, one can proceed to
Login
Most HPC Systems are unix-based environments with shell (commandline) access.
To log in, one usually uses ssh [4] to reach the respective Login Nodes (Computers reserved for the login of users).
| IT Center - RWTH Aachen | RRZE - FAU Erlangen | ZIH - TU Dresden |
| cluster.rz.rwth-aachen.de | cshpc.rrze.fau.de | taurus.hrsk.tu-dresden.de |
Once there, the user can interact with the system and run (very small) programs to generally test the system/software.
Schedulers or How-To-Run-Applications-on-a-supercomputer
To run any significant program or workload on a supercomputer, generally schedulers [5] are employed. Except from the above-mentioned Login Nodes there are usually far more Backend Nodes (Computers exclusively reserved for computing). The scheduler decides who gets how many of those for what time.
In order to run your application with that, you have to tell the Scheduler, what your application needs in term of
- time
- compute resources (how many cpus/sockets/nodes)
- memory resources (how much RAM/storage)
- how to actually execute your application
which obviously has to fit within the boundaries of the running system. If you ask for more than there is, chances are, the scheduler will take this job and wait until you buy and still the missing hardware -> forever. Information over the available hardware can be found in the following table.
This ususally is done with a Jobscript. When you have this jobscript ready with the help of jobscript-examples, colleagues or the Support, you can submit it to the respective Batch-Scheduler.
| IT Center - RWTH Aachen [6] | RRZE - Erlangen [7] | ZIH - Dresden [8] |
| LSF | SLURM | |
After this the application is executed when a set of nodes (computers) are allocated the your 'job' by the scheduler. Usually there is (optionally) Email notification on start/finish of jobs. If the specified time runs out, before your application finishes and exits, it will be terminated.
Modules or How-To-Use-Software-Without-installing-everything-yourself
A lot of applications rely on 3rd party software. One prominent example beeing compilers, this software is usually loadable with the module system. Depending on the