Development and Testing

Revision as of 13:28, 19 July 2016 by Taylor (talk | contribs)
Jump to navigation Jump to search

If you need to develop code (i.e., the standard edit, build, test cycle) or test your workflows and scripts before submitting batch jobs, you should do so within an interactive development session under SLURM. The software environment on the nodes within the dev partition is kept consistent with that of the compute servers so you can run jobs and get an accurate idea of what resources are needed to successfully complete your jobs.

Please remember that you are not allowed to run user applications on the login servers. Interactive work of any kind must be performed on a "dev" server within an interactive SLURM session.


Connect to the cluster (ssh and use SLURM to start a developmental session.

For example, to get a one-hour session with the default 1 processor core and 2gb of memory:

$ module load ufrc
$ srundev --time=04:00:00

The srundev command is a wrapper around the srun --partition=hpg2-dev --pty bash -i command.

Other SLURM directives can also be added to request more processors or memory. For example:

$ module load ufrc
$ srundev --time=60 --cpus-per-task=4 --mem-per-cpu=4gb
  • The default time limit for the hpg2-dev partition is 00:10:00 (10 minutes). The maximum time limit in the dev partition is 12 hours.
  • Either your of your primary or burst QOS may be used when requesting an interactive session.
  • If your resources are fully utilized in both the primary and burst QOS, you will not be able to obtain resources for an interactive session until resources are freed.