Difference between revisions of "UCVM on Compute Nodes"
From SCECpedia
Jump to navigationJump to search| Line 1: | Line 1: | ||
Examples of running UCVM Query on compute nodes on Discovery | Examples of running UCVM Query on compute nodes on Discovery | ||
| − | == | + | == Running on dedicated compute nodes == |
| + | Basic Reasons for using compute nodes | ||
| + | * login (headnode) is shared by all users. | ||
| + | * compute nodes are dedicated to your job (while in use) and not shared | ||
| + | |||
Information To Prepare: | Information To Prepare: | ||
| − | * scalloc - command that will reserve a dedicated | + | * scalloc - command that will reserve a dedicated compute node for your program. |
** Using dedicated worker nodes should let your program run faster than shared headnode | ** Using dedicated worker nodes should let your program run faster than shared headnode | ||
* Number of tasks - typically 1 unless running MPI codes | * Number of tasks - typically 1 unless running MPI codes | ||
| Line 13: | Line 17: | ||
** CARC offers "no-cost" allocations to University researchers that request them | ** CARC offers "no-cost" allocations to University researchers that request them | ||
** Allocation will also include dedicated disk storage on CARC /project filesystem (e.g. /project/maechlin_162 /project/scec_608) | ** Allocation will also include dedicated disk storage on CARC /project filesystem (e.g. /project/maechlin_162 /project/scec_608) | ||
| + | |||
* Example command for running program on discovery: | * Example command for running program on discovery: | ||
**%salloc --ntasks=1 --time=1:00:00 --account=scec_608 | **%salloc --ntasks=1 --time=1:00:00 --account=scec_608 | ||
Revision as of 03:43, 26 April 2021
Examples of running UCVM Query on compute nodes on Discovery
Contents
Running on dedicated compute nodes
Basic Reasons for using compute nodes
- login (headnode) is shared by all users.
- compute nodes are dedicated to your job (while in use) and not shared
Information To Prepare:
- scalloc - command that will reserve a dedicated compute node for your program.
- Using dedicated worker nodes should let your program run faster than shared headnode
- Number of tasks - typically 1 unless running MPI codes
- Expected max duration of program : Format HH:MM:SS
- Longer runtimes can
- HPC systems typically have max runtime (e.g. 24:00:00 or 48:00:00).
- Must make arrangements with HPC system operates for longer runtimes
- allocation account - who's allocation will be charged for computing time
- CARC offers "no-cost" allocations to University researchers that request them
- Allocation will also include dedicated disk storage on CARC /project filesystem (e.g. /project/maechlin_162 /project/scec_608)
- Example command for running program on discovery:
- %salloc --ntasks=1 --time=1:00:00 --account=scec_608
Example profile query
%ucvm_query -f /project/scec_608/<username>/ucvm_bin/conf/ucvm.conf -m cvmsi < rpv.in > rpv_cvmsi.out
- ucvm_query -f /project/maechlin_162/ucvm_bin/conf/ucvm.conf -m cvmsi < rpv.in > rpv_cvmsi.out
slurm batch script
- %cat ucvm_query.job
- %sbatch ucvm_query.job
- %squeue -u maechlin
- %cat rpv_cvmsi.out
