Queues (Resource groups/Job classes)
Interactive job services
Apart from login nodes, interactive nodes (environment), which have the same architecture as compute nodes, are also available. Interactive nodes allow for the execution of programs interactively through the executive of interactive jobs, so please use these nodes for debugging programs and other relevant purposes.
Wisteria-O System : Limiting values for queues
| Queues | Number of nodes | Limiting time (time lapsed) | Memory (GiB) |
|---|---|---|---|
|
interactive-o (interactive-o_n1) (interactive-o_n12) |
1 2 ～ 12 |
10 min |
28 28 |
- Tokens are not consumed.
- Limiting time of "interactive-o_n1" has been changed. (August 2nd, 2022)
Wisteria-A System : Limiting values for queues
| Queues | Number of nodes Number of GPU |
Limiting time (time lapsed) | Memory (GiB) |
|---|---|---|---|
| interactive-a | 1 node | 10 min | 448 |
| share-interactive | 1GPU | 10 min | 56 |
- Tokens are not consumed.
Batch job services
When occupying nodes for a fixed period of time to carry out batch processing, the job is executed as a batch job. (As it is not compatible with the job execution script used in the Oakbridge-CX System etc., it is necessary to create a new script.)
Wisteria-O System: Limiting values for queues
| Queues | Number of nodes | Limiting time (time lapsed) | Memory (GiB) |
|---|---|---|---|
| debug-o | 1 ～ 144 | 30 min | 28 |
| short-o | 1 ～ 72 | 8 hours | 28 |
|
regular-o (small-o) (medium-o) (large-o) (x-large-o) |
1 ～ 144 145 ～ 576 577 ～ 1152 1153 ～ 2304 |
48 hours 〃 〃 24 hours |
28 〃 〃 〃 |
| priority-o | 1 ～ 288 | 48 hours | 28 |
- It is possible to submit jobs to your preferred queue as long as you have a sufficient number of tokens.
- "priority-o" is a priority usage node group, so its token consumption factor is 1.50.
- It is necessary to assign either "debug-o", "short-o", "regular-o" or "priority-o" as the queue name when submitting a job. When assigning "regular-o" queues for either of the internal names will be submitted in accordance with the number of nodes. (It is not possible to submit jobs by assigning individual internal names such as "small-o" or "large-o".)
Wisteria-A System: Limiting values for queues
| Queues | Number of nodes | Limiting time (time lapsed) | Memory (GiB) |
|---|---|---|---|
| debug-a | 1 | 30 min | 448 |
| short-a | 1 ～ 2 | 2 hours | 448 |
|
regular-a (small-a) (medium-a) (large-a) |
1 ～ 2 3 ～ 4 5 ～ 8 |
48 hours 〃 24 hours |
448 〃 〃 |
| Queues | Number of GPU | Limiting time (time lapsed) | Memory (GiB) |
|---|---|---|---|
| share-debug | 1, 2, 4 | 30 min | 56 |
| share-short | 1, 2, 4 | 2 hours | 56 |
|
share (share-1) (share-2) (share-4) |
1 2 4 |
48 hours 〃 24 hours |
56 〃 〃 |
- It is possible to submit jobs to your preferred queue as long as you have a sufficient number of tokens.
- It is necessary to assign either "debug-a", "short-a", "regular-a", "share-debug", "share-short" or "share" as the queue name when submitting a job. When assigning either "regular-a" or “share” queues for either of the internal names will be submitted in accordance with the number of nodes and GPU. (It is not possible to submit jobs by assigning individual internal names such as "small-a" or "large-a".)
Pre-post services
For the pre- or post-processing of analytical data such as visualization, it is possible to use nodes of the same configuration as login nodes interactively as interactive jobs.
Wisteria/BDEC-01 System: Limiting values for queues
■No reservations| Queues | Number of nodes | Limiting time (time lapsed) | Memory (GiB) |
|---|---|---|---|
| prepost | 1 | 6 hours | 340 |
- Tokens are not consumed.
■With reservations
※You will be notified of the queue name when you make a reservation.
| Queues | Number of nodes | Limiting time (time lapsed) | Memory (GiB) |
|---|---|---|---|
| prepost1_n1 ～ prepost4_n1 |
1 | 1 ～ 6 hours | 340 |
| prepost1_n4 | 1 ～ 4 | 1 ～ 6 hours | 340 |
| prepost1_n8 | 1 ～ 8 | 1 ～ 6 hours | 340 |
- Tokens are not consumed.