| Table of Contents |
|---|
...
If your job does not use the system openmpi, or does not use MPI, then any desired core binding will need to be set up with whatever mechanism the software uses. Otherwise, there will be no core binding. Again, that may not be a major issue. If your job does not work well with HT then run on a number of cores equal to half of the number of slots requested and the OS scheduler will minimize contention.
new SGE utilities
While SoGE is very similar to previous versions of SGE there are some new utilities that people may find of interest. There are manual pages for each of these.
...
| Full Resource Name | Shortcut Resource Name | Notes |
|---|---|---|
| std_mem deprecated | sm deprecated | use mem_128G |
| mid_mem deprecated | mm deprecated | use mem_256G |
| high_mem deprecated | hm | use mem_512G |
| mem_96G | 96G | |
| mem_128G | 128G | |
| mem_192G | 192G | |
| mem_256G | 256G | |
| mem_512G | 512G | |
| cpu_arch | cpu_arch |
|
| datacenter | dc |
|
| fabric | fabric |
* no high speed interconnect fabric |
| gpu deprecated | gpu deprecated | Use ngpus instead. |
| gpu_k80 | k80 | |
| gpu_p100 | p100 | |
| gpu_p40 | p40 | |
| gpu_titanv | titanv | |
| gpu_1080ti | 1080ti | |
| ngpus | ngpus | Specify the number of GPU devices that you wish to use |
GPU resources
If you wish to use a compute node that contains a GPU then it must be explicitly requested in some form. The table above lists the Boolean resources for selecting a specific GPU, or any one of the types, with the generic gpu resource.
For example, if you run a job in the all.q queue and want to use a node with a GPU, but do not care which type,
qsub -l gpungpus=true1
If you specifically wanted to use a node with a P100 GPU,
...
In all cases, requesting any of the GPU Boolean resources will set the ngpus resource value to 1 to signify to the scheduler that 1 GPU device is required. If your job needs more than one GPU than that can be specified explicitly with the ngpus resource. For example,
qsub -l ngpus=2
| Info |
|---|
Currently, there are no Argon nodes that have more than 2 GPUs. |
Note that requesting one of the *-GPU queues will automatically set ngpus=1 if that resource is not otherwise set. However, you will have to know what types of GPUs are in those queues if you need a specific type. Investor queues that have a mix of GPU and non-GPU nodes, ie., without the -GPU suffix will need to make a request for a GPU explicit. Since ngpus is a consumable resource, once the resource, the GPU device, is in use, then it is not available for other jobs on that node until it is freed up. If you wish to run non-GPU jobs on the node in tandem with a GPU job then specify ngpus=false0 for the non-GPU job(s).
| Note |
|---|
Setting |
In addition to the ngpus resource there some other non-Boolean resources for GPU nodes that could be useful to you. With the exception of requesting free memory on a GPU device these are informational.
...