Skip to content
Snippets Groups Projects
Commit 239e55f4 authored by Morris Jette's avatar Morris Jette
Browse files

Update power change interval documentation

Intervals below 10 seconds on a Cray system will occasionally
  result in making scheduling decisions based upon old power
  consumption data. May even require larger values for larger
  systems.
parent 12c8d24d
No related branches found
No related tags found
No related merge requests found
...@@ -32,6 +32,10 @@ Currently valid options are: ...@@ -32,6 +32,10 @@ Currently valid options are:
<li><b>balance_interval=#</b> - <li><b>balance_interval=#</b> -
Specifies the time interval, in seconds, between attempts to balance power Specifies the time interval, in seconds, between attempts to balance power
caps across the nodes. caps across the nodes.
This also controls the frequency at which Slurm attempts to collect current
power consumption data (old data may be used until new data is available from
the underlying infrastructure and values below 10 seconds are not recommended
for Cray systems).
The default value is 30 seconds. The default value is 30 seconds.
Supported by the power/cray plugin.</li> Supported by the power/cray plugin.</li>
<li><b>capmc_path=/...</b> - <li><b>capmc_path=/...</b> -
...@@ -215,8 +219,6 @@ to be distributed over 9 nodes or 184 watts per node.</p> ...@@ -215,8 +219,6 @@ to be distributed over 9 nodes or 184 watts per node.</p>
power cap to the minimum value before powering it down. Also set the default power cap to the minimum value before powering it down. Also set the default
power cap of each node to the minimum value as that will be used at power up power cap of each node to the minimum value as that will be used at power up
time.</li> time.</li>
<li>We need to determine how the current power consumption data is gathered
and determine accuracy of that data.</li>
<li>Cray permits independent power capping for accelerators (GPUs or MICs), <li>Cray permits independent power capping for accelerators (GPUs or MICs),
which is not currently used by Slurm.</li> which is not currently used by Slurm.</li>
<li>Current default values for configuration parameters should probably be <li>Current default values for configuration parameters should probably be
...@@ -227,6 +229,6 @@ to be distributed over 9 nodes or 184 watts per node.</p> ...@@ -227,6 +229,6 @@ to be distributed over 9 nodes or 184 watts per node.</p>
balance_interval and synchronizing changes may be difficult</li> balance_interval and synchronizing changes may be difficult</li>
</ul> </ul>
<p style="text-align:center;">Last modified 10 March 2015</p> <p style="text-align:center;">Last modified 12 March 2015</p>
<!--#include virtual="footer.txt"--> <!--#include virtual="footer.txt"-->
...@@ -1457,6 +1457,10 @@ Options current supported by any plugins are listed below. ...@@ -1457,6 +1457,10 @@ Options current supported by any plugins are listed below.
\fBbalance_interval=#\fR \fBbalance_interval=#\fR
Specifies the time interval, in seconds, between attempts to rebalance power Specifies the time interval, in seconds, between attempts to rebalance power
caps across the nodes. caps across the nodes.
This also controls the frequency at which Slurm attempts to collect current
power consumption data (old data may be used until new data is available from
the underlying infrastructure and values below 10 seconds are not recommended
for Cray systems).
The default value is 30 seconds. The default value is 30 seconds.
Supported by the power/cray plugin. Supported by the power/cray plugin.
.TP .TP
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment