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.
Reedbush-U System: Limiting values for job classes
Note: Operation for Reedbush-U has been terminated. (June 30, 2020)
| Queues | Number of nodes | Limiting time (time lapsed) | Memory (GB) |
|---|---|---|---|
| (u-interactive) u-interactive_1 u-interactive_4 |
1 2 ～ 4 |
30 min 10 min |
244 244 |
- Tokens are not consumed.
Reedbush-H System: Limiting values for job classes
| Queues | Number of nodes | Limiting time (time lapsed) | Memory (GB) |
|---|---|---|---|
| (h-interactive) h-interactive_1 h-interactive_2 |
1 2 |
244 244 |
- Tokens are not consumed.
- Limiting time of "h-interactive" has been changed. (September 27th, 2018)
Reedbush-L System: Limiting values for job classes
| Queues | Number of nodes | Limiting time (time lapsed) | Memory (GB) |
|---|---|---|---|
| (l-interactive) l-interactive_1 l-interactive_2 l-interactive_4 |
1 2 3 ～ 4 |
24 h 6 h 1 h |
244 〃 〃 |
- Tokens are consumed.
- New queues, "l-interactive_2" and "l-interactive_4" have been created. (April 1st, 2020)
Batch job services (Applicable from 1 April 2018)
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 FX10, Oakforest-PACS systems, etc., it is necessary to create a new script.)
Reedbush-U System: Limiting values for job classes
Note: Operation for Reedbush-U has been terminated. (June 30, 2020)
| Queues | Number of nodes | Limiting time (time lapsed) | Memory (GB) |
|---|---|---|---|
| u-debug | 1 ～ |
30 min | 244 |
| u-short | 1 ～ 8 | 4 h | 244 |
| (u-regular) u-small u-medium u-large u-x-large |
4 ～ 16 17 ～ 32 33 ～ 64 65 ～ 128 |
48 h 48 h 48 h 24 h |
244 244 244 244 |
- It is possible to submit jobs for any queues as long as you have remaining tokens.
- For "u-small," "u-medium," "u-large," and "u-x-large," assign "u-regular" when submitting the job.
- The maximum number of nodes at "u-debug" has been changed. (August 31st, 2018)
Reedbush-U System: Limiting values for temporary job classes
Note: Operation for Reedbush-U has been terminated. (June 30, 2020)
| Queues | Number of nodes | Limiting time (time lapsed) | Memory (GB) |
|---|---|---|---|
| u-small-ext | 4 ～ 16 | 6 h | 244 |
- "u-small-ext" shares 64 nodes with "h-regular". The priority of "u-small-ext" is lower than "h-regular".
For this reason, the job in "u-small-ext" might not start running for long time if "h-regular" is crowded. - Please use "u-small-ext" for jobs using CPU only.
- Because communication performance of Reedbush-H is different from Reedbush-U, running time of jobs might be different from Reedbush-U.
Reedbush-U: Infiniband EDR (100Gbps)
Reedbush-H: Infiniband FDR ( 56Gbps) ×2 - We might review the settings, including repeal, according to the overall usage status of Reedbush.
Reedbush-H System: Limiting values for job classes
| Queues | Number of nodes | Limiting time (time lapsed) | Memory (GB) |
|---|---|---|---|
| h-debug | 1 ～ 4 | 30 min | 244 |
| h-short | 1 ～ 4 | 2 h | 244 |
| (h-regular) h-small h-medium h-large h-x-large |
1 ～ 4 5 ～ 8 9 ～ 16 17 ～ 32 |
48 hour 48 hour 48 hour 24 hour |
244 244 244 244 |
- It is possible to submit jobs for any queues as long as you have remaining tokens.
- For "h-small," "h-medium," "h-large," and "h-x-large," assign "h-regular" when submitting the job.
Reedbush-L System: Limiting values for job classes
| Queues | Number of nodes | Limiting time (time lapsed) | Memory (GB) |
|---|---|---|---|
| (l-regular) l-small l-medium l-large |
1 ～ 4 5 ～ 8 9 ～ 16 |
168 h 168 h 168 h |
244 244 244 |
- It is possible to submit jobs for any queues as long as you have remaining tokens.
- For "l-small," "l-medium," and "l-large," assign "l-regular" when submitting the job.
Points to note when using tokens
Please read carefully the following points to note when using tokens. Please also refer to the page on tokens, where explanations about tokens and FAQ are provided.- Tokens are consumed each time a batch job is executed and an interactive job (Reedbush-L) is executed.
- Tokens consume an amount of time calculated as a product of node-hours “Time lapsed × Number of nodes × Consumption coefficient.”
- For jobs that exceed the number of nodes applied for, the consumption coefficient is set at a higher level for the number of nodes in excess.
- The consumption coefficient differs based on the course used, system used and the number of nodes specified for the job.
- It is possible to add tokens only when there are spare calculation resources.
- There is no guarantee that all tokens can be used within the period in which use is permitted. As use of the tokens is only allowed during the validity period in which use is permitted, even if there are tokens remaining, they cannot be carried out to the next fiscal year or refunded.
Prepost Service
"Prepost" queue can be used for pre-processing or post-processing of analytical data such as visualization. It can be used interactively as an interactive job.
Reedbush System: Limiting values for job classes
| Queues | Number of nodes | Limiting time (time lapsed) | Memory (GB) |
|---|---|---|---|
| prepost | 1 | 6 h | 500 |
Please see the "Prepost Service (Reedbush)" for detail.