Machine Learning tutorial
|This site replaces the former Compute Canada documentation site, and is now being managed by the Digital Research Alliance of Canada. |
Ce site remplace l'ancien site de documentation de Calcul Canada et est maintenant géré par l'Alliance de recherche numérique du Canada.
This page is a beginner's manual concerning how to port a machine learning job to one of our clusters.
Step 1: Remove all graphical display
Edit your program such that it doesn't use a graphical display. All graphical results will have to be written on disk, and visualized on your personal computer, when the job is finished. For example, if you show plots using matplotlib, you need to write the plots to image files instead of showing them on screen.
Step 2: Archiving a data set
Shared storage on our clusters is not designed to handle lots of small files (they are optimized for very large files). Make sure that the data set which you need for your training is an archive format like
tar, which you can then transfer to your job's compute node when the job starts. If you do not respect these rules, you risk causing enormous numbers of I/O operations on the shared filesystem, leading to performance issues on the cluster for all of its users. If you want to learn more about how to handle collections of large number of files, we recommend that you spend some time reading this page.
Assuming that the files which you need are in the directory mydataset:
$ tar cf mydataset.tar mydataset/*
The above command does not compress the data. If you believe that this is appropriate, you can use tar czf.
Step 3: Preparing your virtual environment
Create a virtual environment in your home space.
For details on installation and usage of machine learning frameworks, refer to our documentation:
Step 4: Interactive job (salloc)
We recommend that you try running your job in an interactive job before submitting it using a script (discussed in the following section). You can diagnose problems more quickly using an interactive job. An example of the command for submitting such a job is:
$ salloc --account=def-someuser --gres=gpu:1 --cpus-per-task=3 --mem=32000M --time=1:00:00
Once the job has started:
- Activate your virtual environment.
- Try to run your program.
- Install any missing modules if necessary. Since the compute nodes don't have internet access, you will have to install them from a login node. Please refer to our documentation on virtual environments.
- Note the steps that you took to make your program work.
Now is a good time to verify that your job reads and writes as much as possible on the compute node's local storage ($SLURM_TMPDIR) and as little as possible on the shared filesystems (home, scratch and project).
Step 5: Scripted job (sbatch)
You must submit your jobs using a script in conjunction with the sbatch command, so that they can be entirely automated as a batch process. Interactive jobs are just for preparing and debugging your jobs, so that you can execute them fully and/or at scale using sbatch.
Important elements of a sbatch script
- Account that will be "billed" for the resources used
- Resources required:
- Number of CPUs, suggestion: 6
- Number of GPUs, suggestion: 1 (Use one (1) single GPU, unless you are certain that your program can use several. By default, TensorFlow and PyTorch use just one GPU.)
- Amount of memory, suggestion: 32000M
- Duration (Maximum Béluga: 7 days, Graham and Cedar: 28 days)
- Bash commands:
- Preparing your environment (modules, virtualenv)
- Transferring data to the compute node
- Starting the executable
#!/bin/bash #SBATCH --gres=gpu:1 # Request GPU "generic resources" #SBATCH --cpus-per-task=3 # Refer to cluster's documentation for the right CPU/GPU ratio #SBATCH --mem=32000M # Memory proportional to GPUs: 32000 Cedar, 47000 Béluga, 64000 Graham. #SBATCH --time=0-03:00 # DD-HH:MM:SS module load python/3.6 cuda cudnn SOURCEDIR=~/ml-test # Prepare virtualenv source ~/my_env/bin/activate # You could also create your environment here, on the local storage ($SLURM_TMPDIR), for better performance. See our docs on virtual environments. # Prepare data mkdir $SLURM_TMPDIR/data tar xf ~/projects/def-xxxx/data.tar -C $SLURM_TMPDIR/data # Start training python $SOURCEDIR/train.py $SLURM_TMPDIR/data
Checkpointing a long-running job
We recommend that you checkpoint your jobs in 24 hour units. Submitting jobs which have short durations ensures they are more likely to start sooner. By creating a daisy chain of jobs, it is possible to overcome the seven day limit on Béluga.
- Modify your job submission script (or your program) so that your job can be interrupted and continued . Your program should be able to access the most recent checkpoint file. (See the example script below).
- Verify how many epochs (or iterations) can be carried out in a 24 hour unit.
- Calculate how many of these 24 hour units you will need: n_units = n_epochs_total / n_epochs_per_24h
- Use the argument --array 1-<n_blocs>%1 to ask for a chain of n_blocs jobs.
The job submission script will look like this:
#!/bin/bash #SBATCH --array=1-10%1 # 10 is the number of jobs in the chain #SBATCH ... module load python/3.6 cuda cudnn # Prepare virtualenv ... # Prepare data ... # Get most recent checkpoint CHECKPOINT_EXT='*.h5' # Replace by *.pt for PyTorch checkpoints CHECKPOINTS=~/scratch/checkpoints/ml-test LAST_CHECKPOINT=$(find $CHECKPOINTS -maxdepth 1 -name "$CHECKPOINT_EXT" -print0 | xargs -r -0 ls -1 -t | head -1) # Start training if [ -z "$LAST_CHECKPOINT" ]; then # $LAST_CHECKPOINT is null; start from scratch python $SOURCEDIR/train.py --write-checkpoints-to $CHECKPOINTS ... else python $SOURCEDIR/train.py --load-checkpoint $LAST_CHECKPOINT --write-checkpoints-to $CHECKPOINTS ... fi