The following is OCTOPUS job class table. Please note that the job classes differ depending on your usage.
General Purpose CPU nodes
| Usage | Job Class | Maximum Elapsed Time | Maximum Number of Cores | Maximum Size of Memory | Maximum Number of Nodes | Remarks |
|---|---|---|---|---|---|---|
| Shared Use | OCT | 120 hours | 32,768 cores (256 cores/node) | 92.75 TiB (742 GiB/node) | 128 nodes | Dedicated use within nodes |
| OCT-H | 120 hours | 32,768 cores (256 cores/node) | 92.75 TiB (742 GiB/node) | 128 nodes | Dedicated use within nodes High Priority(*1) |
|
| OCT-S | 120 hours | 128 cores | 371 GiB | 1 node | Allows multiple jobs to be assigned to a single node.(*2) | |
| DBG | 10 minutes | 512 cores (256 cores/node) | 1,484 GiB (742 GiB/node) | 2 nodes | For debug use | |
| INT | 10 minutes | 512 cores (256 cores/node) | 1,484 GiB (742 GiB/node) | 2 nodes | For interactive use | |
| VA | 120 hours | 256 cores | 742 GiB | 1 node | For pseudo-quantum annealing | |
| Dedicated Use | myOCT | Unlimited | 256 cores × number of dedicated nodes | 742 GiB × number of dedicated nodes | number of dedicated nodes | Apply separately |
*1: The execution waiting time is shortened because of the high priority, but OCTOPUS point consumption becomes large.
*2: Allows resource sharing with other jobs within one node. A queue that allows resource sharing within a single node with other jobs. Point consumption becomes small, but may be affected by other jobs.
Resource Limitations
For each queue, there are limits on elapsed time, number of CPUs, size of memory, and number of nodes.
When describing them in a job script, it is necessary to specify that the limits are not exceeded.
