Aalto: if you still experience this error
send your Aalto username to Enrico to fix it
Please write your answer here below
I process health data from multiple participants, so my analysis pipeline could work on participants' data in parallel. Every job can correspond to one participant. At the end I gather everything (group statistics).
I have some simulation code that takes as input parameter a location in the brain. In the end, I want the results for 4000 locations. Each location can be run in parallel. Is creating an array job of size 4000 too much?
Train image data scenes for semantic segmentation.. using ML tools,
Imaging data from ~40k individuals that each need processing that isn't super intensive. I'm trying to figure out now what the optimal division is (i.e. 400x100 jobs, or 80x500 jobs etc or something in the middle?).
Mostly deep learning related stuff. It would be great to know how to efficiently parallelise data I/O
Ask anything, write always at the bottom (please include your organization to the question if it is something specific to Aalto or University of Helsinki)
-x <nodelist>
. By nodelist in SLURM is meant a comma separated node1,node2,node67
or node[1-5],node8
etc. The list of nodes sinfo -N
.srun python my_python_script.py
and srun Rscript my_r_script.R
. Make sure you have the proper module load
commands in your SBATCH script though.slurm h
resource usage for that step. So you don't need to do "srun cd $WRKDIR", but you want to dosrun ...
is a step from the SLURM point of view, one can set different requirements per step, and there can be as many steps in the SLURM script as you wish. Steps may have different parameters, like you allocate an amount of of CPUs and meory in total and a particular step will use only part of the allocated memory and only limited number of the allocated CPUs, i.e. a way to share resources inside the SBATCH script (srun --mem 1G --ntasks 4 ...
). Steps can be run in parallel (srun ... &
). Step are registred and seen as a separate task within the job run, (slurm history
) thus one can control memory usage etc. srun ...
also replaces mpirun for the MPI jobs and makes sure your app gets all the needed parallel job related parameters. As mentioned previously, SLURM script is nothing else than a SHELL script, so common best practice: commands like cd
, module load ...
or BASH programming logic should use just normal bash syntax, while all the core applications that you run, or anything that uses resources heavily like data copying/extracting makes sense to start with srun
, thus you can analyze the timing, memory usage etc later.slurm h
show recent jobs. For more advanced querying on your usage there is a command called sacct
. Another useful one is seff JOBID
to give you efficiency about the job you just ran. We also have an utility called "jobstats
" to monitor the I/O of your job (it can be important for data intensive things, e.g. you have lots of data or you use GPUs which want lots of data at once, i.e. I/O can become a bottleneck). Some link to docs:slurm features
, see NODES(A/I/O/T) column. There A stands for Allocated Nodes, I is Idling, O is some Other status (failed, drained etc) and T is Total. That is the best estimate of the cluster usage at the moment.https://scicomp.aalto.fi/triton/tut/serial/#exercises
cd $WRKDIR
and organize your data overthere.slurm watch q
and watch slurm q
? I hope it doesn't cause any issues?
watch
does basically the same thing for any program./usr/bin/slurm
you'll see that slurm watch ...
is exactly the watch -n 15 --no-title
that does the job. So, no diff.Will each of the array jobs have the specified time and mem or will they share the recourses?
How to specify the machine we want to run sbatch ? For example not all of them support vector operations.
srun will automatically run parallel for different samples?
Will you have a course for programming with GPUs (CUDA)? :)
Does local computer impact the parallel job?
.
.
.
Before you leave, please write down something that was useful/positive, and something that could be improved for future courses. Thank you! (if you are not logged in on hackmd, then feedback is fully anonymous)
Thank you, it was very useful! Materials is really well done and I will surely go back to it. I liked that the teacher in the zoom exercises was slowly showing what to do. I think there was not enough time for exercises, so I feel I have to do them by myself later.
I hope I'm able to run some of my Julia code on Triton now. Thank you!
Great sharing, thanks a lot! I want to implement training with pytorch on Triton.
Thank you very much, very useful course. I will start using TRITON for my simulations - I might have visit you at the Garage for some help :)
Thanks for the quick but useful introduction to working with the Triton cluster! I'm not sure if I will be able to make my codes 100% efficient in both CPU and GPU parts but I look forward to your help when I'm stuck in the future! :)
Compressed handbook of Triton commands "Triton Cookbook".
^that is the cheatsheet (search for cheatsheet in our documentation)
-Thanks!
.
Overall the sessions were awesome, the last part of GPU and parallelization might deserve longer timeslot IMO since they are also more difficult than the rest.
Session was awesome. Is it possible to share the email contact for help in future here.
The session progressed with intense flow. It was easy to dive in, follow the dialogue and forget else. On the other hand, losing focus riskes one to get dropped on the topic. I liked really much the dialogue between the instructors, as they were explaining to each other the concepts and naturally asked and answered all those obvious questions.
I wish there would have been some more time to try out the examples, I didn't have the command line routine so I was struggling to even copy paste and run the examples during the exercise breaks. Perhaps make longer day two or move something to day one?
Thanks so much. It's very helpful.
Recordings of everything will be (and are already) at https://www.youtube.com/playlist?list=PLZLVmS9rf3nN_tMPgqoUQac9bTjZw8JYc
Daily garage at: https://scicomp.aalto.fi/help/garage/
^^^ Please write above this line ^^^