In this page, the "point" under the shared use mode is explained as well as how it is used.
What is point?
Under the shared use mode, the amount of computational resources is managed and controlled on the basis of "point". Thanks to this point system, users are not required to complete applications for each node type, meaning that just one application allows you to use every type of nodes. points consumed on each node type is measured as follows.
Point consumption = Node-hours x Consumption coefficient x Seasonal coefficient x Fuel coefficient
The words are described in detail below.
Node-hour
1 node-hour = the computational resource amount of 1 hour computation using 1 node. In the case that you have 30 node-hours, it means that you can have one-hour computation using 30 nodes or three-hour computation using 10 nodes, etc...
node-hours is calculated as follows.
node-hours = Number of nodes x Computing time(unit:hour)
Please see below for the details of node-hour.
Node-hour in shared use
Consumption coefficient
Consumption coefficient is the static number set based on power consumption on each node.
OCTOPUS
Node Type | Consumption coefficient |
---|---|
General purpose CPU node | 0.1040 |
GPU node | 0.4346 |
XeonPhi node | 0.0836 |
Large-scale shared-memory node | 0.7406 |
SQUID
Node type | high-priority | normal-priority | share |
---|---|---|---|
General purpose CPU node | 0.3746 | 0.2998 | 0.2248 |
GPU node | 2.2934 | 1.8348 | 1.3762 |
Vector node | 1.4140 | 1.1312 | 0.8484 |
Seasonal coefficient
Seasonal coefficient is the number set based on utilization situation on each node type in the previous fiscal year. The purpose of introducing this coefficient is to better improve off-season utilization and then alleviate peak-time congestion. For example, if you run a job when the seasonal coefficient is 0.8, the amount of OCTOPUS point's consumption is 20 percent lower than usual. It is set between 0 to 1, so the cost never becomes higher than usual. We will disclose annual seasonal coefficient here at the beginning of April in order to make it easy for users to lay calculation plan.
OCTOPUS
We set "1" as Seasonal coefficient in 2023.
SQUID
We set "1" as Seasonal coefficient in 2023.
Fuel coefficient
-
We will establish "fuel coefficient" and set prices in accordance with electric rates. We will initially set it to "1" for 2023 fiscal year, and review it as needed throughout the year. We will notify all users separately if there are any changes.
Examples
-
Using 10 OCTOPUS General pupose CPU nodes for 3 hour (Seasonal coefficient is 1 and Fuel coefficient is 1)
10 × 3 × 0.1040 × 1 × 1 = 3.12
→3.12 OCTOPUS points is consumed. -
Using 10 OCTOPUS GPU nodes for 3 hour (Seasonal coefficient is 1 and Fuel coefficient is 1)
10 × 3 × 0.4346 × 1 × 1 = 13.038
→13.038 OCTOPUS points is consumed. -
Using 10 OCTOPUS General pupose CPU nodes for 3 hour (Seasonal coefficient is 0.8 and Fuel coefficient is 1.2)
10 × 3 × 0.1040 × 0.8 × 1.2 = 2.9952
→2.9952 OCTOPUS points is consumed.
<FYI>
Node-hour you can use in 0.1 million JPY cource (1,000 points) is as follows:
OCTOPUS | Consumption coefficient | Seasonal coefficient | Node-hour |
---|---|---|---|
General purpose CPU node | 0.1040 | 1 | 9,615 node-hours |
GPU node | 0.4346 | 2,300 node-hours | |
XeonPhi node | 0.0836 | 11,960 node-hours | |
Large-scale shared-memory node | 0.7406 | 1,350 node-hours | |
SQUID | Consumption coefficient | Seasonal coefficient | Node-hour |
General purpose CPU node | 0.2998 | 1 | 3,335 node-hours |
GPU node | 1.8348 | 545 node-hours | |
Vector node | 1.1312 | 884 node-hours |
This guide is the case that you consume all 1,000 OCTOPUS points in single node type. Of cource, you can select a node type you want by the job.
How to Check Resource Usage
Please use usage_view command. This command shows the information of node-hours consumed by the user and the user's group. Also, disk usage are displayed. The detail is available from "How to Check Resource Usage".
How to Check for Resource Usage (OCTOPUS) How to Check for Resource Usage (SQUID)
Usage Rule for "point"
- Points are assigned to each group. Points cannot be shared by individual users.
- After consuming all Points, it is impossible to submit / run a job request. As to a computation that is already running, it will finish without being suspended.
- In the case that a job execution is suspended due to system trouble, the points will not be consumed. If this case occurs, we will contact you.