{{METATOC 1-5}}



====== Introduction ======
This page gives best practices and tips on how to use the clusters **Baobab** and **Yggdrasil**.


An HPC cluster is an advanced, complex and always-evolving piece of technology. It's easy to forget details and make mistakes when using one, so don't hesitate to check this section every now and then, yes, even if you are the local HPC guru in your team! There's always something new to learn !

====== First steps ======

You are now ready to start using the HPC clusters. But how do you start ?

For your first steps we recommend the following :
  * Check the [[hpc:best_practices#rules_and_etiquette|Rules and etiquette]].
  * Connect to the login node of the cluster you are planning to use : [[hpc:access_the_hpc_clusters|Access : SSH, X2GO]]
  * Check the rest of this page for best practices and smart use of the HPC resources.
    * [[hpc:best_practices#stop_wasting_resources|This page contains important information]]! You can hog resources and/or wait much longer than you could if you don't request the right amount of time for your job, if you ask too much (or not enough) resources, if you are not using the right partition, etc. 
  * Understand how to load your libraries/application with ''module'': [[applications_and_libraries|Applications and libraries]]
  * Learn how to write a Slurm ''sbatch'' script: [[slurm|Slurm and job management]]

====== Rules and etiquette ======

As a user, you are sharing a fabulous technological beast with hundreds of other researchers. Any research is important (and //yes// we realise //your// research is more important!), nevertheless we expect all of you to respect following rules and etiquette.

  * Have basic knowledge of the [[linux|Linux command line (without GUI) and Bash scripting]].	
  * **Do not use the login node to execute any code**
    * If you do, you are disturbing all other users and this is unacceptable. When this happens we will most likely kill your process and send you an email to make you feel bad.
    * The login node should only be used to compile your code and submit a Slurm job. You must even use Slurm to run your tests. The ''debug-cpu'' and ''debug-gpu'' partitions are dedicated for small tests.
  * Make a fair use of the resources and **do not waste resources** for others.
    * When people waste resources, it increases the waiting time for everyone.
    * The best way to avoid that is by making sure you have a **reasonable estimation** for the resources you need in your sbatch (CPU, memory, duration, etc.) and that you are using the right partition for the job.
	* Read more in the section [[hpc:best_practices#stop_wasting_resources|Stop wasting resources!]]
    * It's fine to ask your colleagues to give you pointers, BUT adapting a script they wrote 5 years ago might not be good for your project.
  * Loading applications and libraries should always be done using ''module''
    * Pro tip: you can even force the version to have consistent results or to survive an OS migration, for example.
    * When an application is not available through ''module'', you can compile binaries in your ''$HOME'' directory and use them on any node of the cluster (since your ''$HOME'' is accessible from any node). Make sure you load the [[hpc:applications_and_libraries#choosing_the_compiler_toolchain|compiler]] with ''module''.
    * You can request the HPC team to install a new software or version of a library in order to load it through ''module''. Check [[hpc/applications_and_libraries#what_do_i_do_when_an_application_is_not_available_via_module|this page]]
  * You **cannot** install new software with ''yum'' (and don't bother with ''apt-get'', we are not running Ubuntu).
  * **You are not ''sudo''** and never will be. 
    * N.B. this is only available for the sacred HPC engineers (Linux-type beard and hoody mandatory)
  * [[hpc:best_practices#think_green|Think green]] : wasting compute resources is **not environmental friendly** as a wasted resource still uses electricity to run and AC to cool down our data centre.


====== Think green ======

By design, an HPC cluster is not the most environmental friendly thing in the world : dozens or sometimes hundreds of servers (compute nodes) are running 24/7. But, it doesn't mean there's nothing you can do about it!

If you are not familiar with IT infrastructures, this can be simplified to this :
  * Computer are powered with **electricity** and produce **heat**. A powerful computer usually produces more heat.
  * **Baobab** has 250+ nodes and **Yggdrasil** has 130+ nodes
  * The heat produced by the nodes needs to be cooled down with Air conditioning (AC) to avoid hardware failure.

The power consumption of Baobab and Yggdrasil is more of less **80kW** **each** (that doesn't include the AC).

The best we can do about it is to make the most of the clusters by using all the resources available and not wasting them.\\

The same goes for the storage. As you [[hpc/storage_on_hpc|already know]] you shouldn't store any personal files on the clusters.

But even with scientific data, if you are storing thousands of files and using hundreds of GB that you don't really need, at some point we will have to buy more storage. The storage servers are no different than compute nodes : they also need electricity to run and AC to be cooled down. So deleting useless files from time to time is a good habit.

Besides the quantity of data, remember it is important //where// you store your data. For instance, we back up the content of your ''$HOME'' every day. Once again, backing up large quantities of data relies on a high speed network, backup tapes, a robot to read/load the tapes, etc.

We still want you to store your files and use the clusters! But we would appreciate if you could keep this in mind next time you wonder if you should keep this 500GB failed output from 3 years old job.

====== Stop wasting resources! ======

Based on the post [[https://hpc-community.unige.ch/t/good-usage-of-resources-on-hpc-cluster/766|Good usage of resources on HPC cluster ]], this section gives you information on how to avoid wasting resources on the clusters.

On a HPC cluster such as Baobab or Yggdrasil, the resources are shared between all the users. For this reason it is important to use them wisely. An allocated resource is unavailable for others during the complete lifespan of the job. The issue arise when the resource is allocated but not used.

N.B. in the HPC world, when we talk about CPU, we usually mean core. In Baobab a standard compute node has 2 physical CPUs and 20 cores. So we say that the node has 20 CPUs.

===== Which resources ? =====

 The resources available on our clusters are:

  * CPUs, which are grouped in [[hpc/slurm#partitions|partitions]]
  * [[hpc/hpc_clusters#compute_nodes|GPGPUs]] which are accelerator for software that support them
  * memory (RAM) per core or per node, 3GB by default
  * disk space
  * time, duration of the computation

===== Single thread vs multi thread vs distributed jobs =====

See [[hpc:slurm#single_thread_vs_multi_thread_vs_distributed_jobs|here]] to be sure you specify the correct configuration for your job type 


===== Bad CPU usage =====

Let's take an example of a **single threaded job**. You should clearly use a partition which allows to request a single CPU, such as ''public-cpu'' or ''shared-cpu'' and ask one CPU only. If you ask too much CPUs, the resources will be reserved for your job but only one CPU will be used. See the screenshot below of such a bad case where 90% of the compute node is idle.

{{ :hpc:wasted_resources_mono_threaded_job_1.png?nolink&450 |}}


===== Bad memory usage =====

Another misuse of HPC resources, is to request too much RAM without using it. Baobab has many older compute nodes with 48GB. If you request for example 40GB of RAM and 1 CPU, only two other CPU of this compute node may be allocated for another job, the remaining will stay unused by lack of memory. This is ok as long as you really use the memory. But in this case, if you job can benefit of more CPU, feel free to request all the other cores of this compute node. You can [[hpc/slurm#memory_and_cpu_usage|check the memory usage]] during the job execution or after.

===== Bad time estimation =====

If you submit a job and request 4 days of compute time and your job run effectively for 10 minutes, your time estimation is bad. It is important for the scheduler (Slurm) that your time estimation is correct. A couple of hours of overestimation is ok. It is also important to have more or less correct time estimation due to the fact that slurm doesn't only put new job in a fifo queue, but has a backfill mechanism that allows to launch a job that is later in the queue sooner if it doesn’t disturb other job. See the picture below ((Source: Scheduling. Slurm Training15. Salvador Martin & Jordi Blasco (HPCNow!).)) for an explanation.

{{ :hpc:fifo_vs_backfill.jpeg?nolink&500 |}}


===== Conclusion =====

You can see on the screenshot below the overall usage of the CPU resource during a whole day.
The goal is to increase this usage to around 80% which is considered the maximum on a general purpose cluster. So, help us to reach this goal and, use the resource wisely!


{{ :hpc:wasted_resources_overall_cpu_baobab.png?nolink&600 |}}


====== How to write a good Slurm sbatch script ======

You need to use the cluster(s) and after reading the rest of the documentation, you are now convinced about making the most of the resources whithout wasting them!

So, what is the best way to do that ?

First of all, a "good" sbatch script doesn't need to be complicated. It needs to reflect your needs and your job's needs.

You should find most answers on the [[hpc/slurm|Slurm]] page and in the official [[https://slurm.schedmd.com/documentation.html|Slurm documentation]].


In any case, those are the questions you should ask yourself :
  * What [[/hpc/best_practices#single_thread_vs_multi_thread_vs_distributed_jobs|type of job]] am I running (single threaded, multi threaded or distributed) ?
    * This will help you choose the parameters ''<nowiki>--ntasks</nowiki>'' and ''<nowiki>--cpus-per-task</nowiki>'' 
  * [[hpc/slurm#which_partition_for_my_job|What partition should I run my job on]] ?
    * This will help you choose the parameters ''<nowiki>--partition</nowiki>''
  * How much memory does my job need ?
    * This will help you choose the parameters ''<nowiki>--mem</nowiki>'', or ''<nowiki>--mem-per-cpu</nowiki>'' 
    * If you need a large amount of RAM, you might also need to choose a ''*-bigmem'' partition.
  * For how long does my job needs to run ?
    * This will help you choose the parameters ''<nowiki>--time</nowiki>'' 
  * Do I want to receive email notification ?
	* This is optional, but you can specify the level of details you want with the ''<nowiki>--mail-type</nowiki>'' parameter

====== Transfer data from cluster to another with ======
===== Rsync =====
This help assumes you want transfer the directory ''<nowiki>$HOME/my_projects/the_best_project_ever</nowiki>'' from baobab to yggdrasil at the same path. You can adapt your case by changing the variables.


__**Rsync options:**__
  * ''<nowiki>-a, --archive</nowiki>''This is equivalent to ''<nowiki>-rlptgoD</nowiki>''. It is a quick way of saying you want recursion and want to preserve almost everything (with ''<nowiki>-H</nowiki>'' being a notable omission). The only exception to the above equivalence is when ''<nowiki>--files-from</nowiki>'' is specified, in which case -r is not implied.
  * ''<nowiki>-i</nowiki>'' turns on the itemized format, which shows more information than the default format
  * ''<nowiki>-b</nowiki>'' makes rsync backup files that exist in both folders, appending ~ to the old file. You can control this suffix with ''<nowiki>--suffix .suf</nowiki>''
  * ''<nowiki>-u</nowiki>'' makes rsync transfer skip files which are newer in dest than in src
  * ''<nowiki>-z</nowiki>'' turns on compression, which is useful when transferring easily-compressible files over slow links
  * ''<nowiki>-P</nowiki>'' turns on --partial and --progress
  * ''<nowiki>--partial</nowiki>'' makes rsync keep partially transferred files if the transfer is interrupted
  * ''<nowiki>--progress</nowiki>''  shows a progress bar for each transfer, useful if you transfer big files
  * ''<nowiki>-n, --dry-run</nowiki>''  perform a trial run with no changes made

1) Go to your directory containing ''<nowiki>the_best_project_ever</nowiki>'':
<code>
(baobab)-[toto@login2 ~]$cd $HOME/my_projects/
</code>

2) Set the variables (or not)
<code>
(baobab)-[toto@login2 my_projects]$ DST=$HOME/my_projects/
(baobab)-[toto@login2 my_projects]$ DIR=the_best_project_ever
(baobab)-[toto@login2 my_projects]$ YGGDRASIL=login1.yggdrasil
</code>
3) Run the rsync
<code>
(baobab)-[toto@login2 my_projects]$ rsync -aviuzPrg ${DIR} ${YGGDRASIL}:${DST}
</code>


====== SWITCHfilesender from the cluster ======

Switch Filesender
Filesender is a service provided by SWITCH for transferring files via http. Normally, files are downloaded via a web browser, but using the CLI is more efficient and we benefit from the Login node's high bandwidth.

In order to avoid having to transfer the files to your local computer it is possible to use the Filesender command line tools as explained below

 

===== Configuring the CLI tools =====
 

Connect to https://filesender.switch.ch then go to the profile tab

{{:hpc:screenshot-2022-01-13-at-15-14-02.png}}

Then click on "Create API secret" to generate a code that will be used to allow you to authenticate

{{:hpc:screenshot-2022-01-13-at-15-14-37.png}}

This will generate a long string like

''ab56bf28434d1fba1d5f6g3aaf8776e55fd722df205197''

Then connect to HPC cluster and run the following commands to download the CLI tool and the configuration


<code>
cd

mkdir ~/.filesender

wget https://filesender.switch.ch/clidownload.php -O filesender.py

wget https://filesender.switch.ch/clidownload.php?config=1 -O ~/.filesender/filesender.py.ini
</code>

You will then need to edit the ''~/.filesender/filesender.py.ini'' file using your preferred tool

You need to enter your username as show in the Filesender profile and the API key that you generated

Note that at present, unlike the other Switch services this is not your EduID account!

<code>
[system]
base_url = https://filesender.switch.ch/filesender2/rest.php
default_transfer_days_valid = 20

[user]
username = Charizard@unige.ch
apikey = ab56bf28434d1fba1d5f6g3aaf8776e55fd722df205197
</code>

==== Transferring files ====


Now that we have done this we can transfer files - note that the modules must be loaded in order to have a python with the required libraries.


  (baobab)-[alberta@login2 ~]$ module load GCC Python

You may need to install some python package before:

  (baobab)-[alberta@login2 ~]$ pip3 install requests urllib3

<code>
(baobab)-[alberta@login2 ~]$ python3 filesender.py -p -r mewtwo@unige.ch master.tar.gz 
Uploading: /home/users/a/alberta/master.tar.gz 0-18408 0%
Uploading: /home/users/a/alberta/master.tar.gz 18408 100%
</code>

A mail will be sent to ''Mewtwo@unige.ch''  who can then download the file


====== HPC cluster user departure procedure ======

**Step 1: Backup and clean up personal data**
  * **Retrieve your personal data** from the **home** and **scratch** directories.
  * **Clean** these directories by removing unnecessary files.

**Step 2 (optional): Organizing and transferring shared data**
  * If you belong to a group, **identify important data** in shared directories.
  * If a data ownership transfer is necessary, send a **request to the HPC team** to transfer ownership to another user, with the group leader's approval.

**Step 3: Transfer confirmation**
  * Ensure the data transfer has been completed and notify the relevant parties.