2019.3.18
There are no plans to change the computational resources of the system in FY2019 from FY2018. The following items are considered to be particularly significant. Please refer to the usage plan of 2019.
Summer power saving period (Jul. - Sep.)
As with last year, there will be no change in the number of provisioned nodes from normal period. However, if there is a strong demand for saving electricity from the university or social situation, there is a possibility that it may change. In the last few years, the energy conservation section of the university has requested the cooperation of 7/1-9/30 for energy saving in the latter half of June. In TSUBAME2, the queue configuration was changed, and peak shift operation was performed to change the number of available nodes during the day and night, but TSUBAME3 has more flexibility in the queue itself, and has achieved significant power saving at all times. , 2018 did not do special operations.
Busy season (Oct. - Mar.)
As in the last year, during busy seasons, we will change the number of parallel executions and the number of concurrent executions to equalize resource usage opportunities.
Execute job
| Apr. - Sep. | Oct. - Mar. | |
|---|---|---|
| Number of concurrently executable jobs per person | 150 jobs | 50 jobs |
| Total number of slots that can be simultaneously executed per person | 2016 slots | 2016 slots |
| Maximum parallelism per job | 72 | 72 |
Node Execute job
| Apr. - Sep. | Oct. - Mar. | |
|---|---|---|
| Number of reservation providing nodes (whole) | 270 nodes | 135 nodes |
| 1 Reservation maximum reservation time | 168 hours(7 days) | 96 hours (4 days) |
| Total number of reservation frames that one group can simultaneously secure | 12960 nodehours | 6480 nodehours |