SCHDOFL parameter - Revision history

DCameron: /* Description */

2017-05-24T11:31:43Z

Description

← Older revision		Revision as of 11:31, 24 May 2017
Line 29:		Line 29:
	<var>[[SCHDOFLZ parameter\|SCHDOFLZ]]</var> performs the same function as <var>SCHDOFL</var> for <var>[[Performance_monitoring_and_tuning#Offloading_Model_204_work_to_zIIP_processors\|zIIP]]</var> (SRB) subtasks. <var>[[SCHDOFLS parameter\|SCHDOFLS]]</var> controls how aggressively MP subtasks are started to help out zIIP subtasks, and how aggressively MP subtasks take work from zIIP subtasks. </p>		<var>[[SCHDOFLZ parameter\|SCHDOFLZ]]</var> performs the same function as <var>SCHDOFL</var> for <var>[[Performance_monitoring_and_tuning#Offloading_Model_204_work_to_zIIP_processors\|zIIP]]</var> (SRB) subtasks. <var>[[SCHDOFLS parameter\|SCHDOFLS]]</var> controls how aggressively MP subtasks are started to help out zIIP subtasks, and how aggressively MP subtasks take work from zIIP subtasks. </p>
	<p>		<p>
	~~Before~~ Model 204 7.7, the minimum allowed value for <var>SCHDOFL</var> is 1. Under Model 204 7.7 and later, it is 0, though it is probably a bad idea to set <var>SCHDOFL</var> to 0 unless the <var>[[MPDELAY parameter\|MPDELAY]]</var> parameter is set to a non-zero value.		Prior to Model 204 7.7, the minimum allowed value for <var>SCHDOFL</var> is 1. Under Model 204 7.7 and later, it is 0, though it is probably a bad idea to set <var>SCHDOFL</var> to 0 unless the <var>[[MPDELAY parameter\|MPDELAY]]</var> parameter is set to a non-zero value.
	</p>		</p>

	[[Category:System parameters]]		[[Category:System parameters]]
	[[Category:Parameters]]		[[Category:Parameters]]

DCameron: /* Description */

2017-05-24T11:17:56Z

Description

← Older revision		Revision as of 11:17, 24 May 2017
Line 27:		Line 27:
	</ul>		</ul>
	<p>		<p>
	<var>[[SCHDOFLZ parameter\|SCHDOFLZ]]</var> performs the same function as <var>SCHDOFL</var> for zIIP (SRB) subtasks. <var>[[SCHDOFLS parameter\|SCHDOFLS]]</var> controls how aggressively MP subtasks are started to help out zIIP subtasks, and how aggressively MP subtasks take work from zIIP subtasks. </p>		<var>[[SCHDOFLZ parameter\|SCHDOFLZ]]</var> performs the same function as <var>SCHDOFL</var> for <var>[[Performance_monitoring_and_tuning#Offloading_Model_204_work_to_zIIP_processors\|zIIP]]</var> (SRB) subtasks. <var>[[SCHDOFLS parameter\|SCHDOFLS]]</var> controls how aggressively MP subtasks are started to help out zIIP subtasks, and how aggressively MP subtasks take work from zIIP subtasks. </p>
	<p>		<p>
	Before Model 204 7.7, the minimum allowed value for <var>SCHDOFL</var> is 1. Under Model 204 7.7 and later, it is 0, though it is probably a bad idea to set <var>SCHDOFL</var> to 0 unless the <var>[[MPDELAY parameter\|MPDELAY]]</var> parameter is set to a non-zero value.		Before Model 204 7.7, the minimum allowed value for <var>SCHDOFL</var> is 1. Under Model 204 7.7 and later, it is 0, though it is probably a bad idea to set <var>SCHDOFL</var> to 0 unless the <var>[[MPDELAY parameter\|MPDELAY]]</var> parameter is set to a non-zero value.

DCameron: /* Description */

2017-05-24T11:13:39Z

Description

← Older revision		Revision as of 11:13, 24 May 2017
Line 22:		Line 22:
	<var>SCHDOFL</var> has no effect if either of these is true: </p>		<var>SCHDOFL</var> has no effect if either of these is true: </p>
	<ul>		<ul>
	<li>MP/204 is not in effect in an Online (<var>NMPSUBS</var> is 0).</li>		<li>MP/204 is not in effect in an Online (<var>[[NMPSUBS_parameter\|NMPSUBS]]</var> is 0).</li>

	<li>The number of active subtasks (<var>AMPSUBS</var>) is set to 0 or 1. (If <var>AMPSUBS</var> is 1, an MP subtask is activated as soon as there is any offloadable work, and it then runs until there is no more offloadable work for it to process.)</li>		<li>The number of active subtasks (<var>AMPSUBS</var>) is set to 0 or 1. (If <var>AMPSUBS</var> is 1, an MP subtask is activated as soon as there is any offloadable work, and it then runs until there is no more offloadable work for it to process.)</li>

DCameron: /* Description */

2017-05-24T11:11:18Z

Description

← Older revision		Revision as of 11:11, 24 May 2017
Line 18:		Line 18:
	This parameter specifies the target number of threads on the MP offload queue per active task. Setting this parameter makes the <var class="product">Model 204</var> MP subtask scheduler more responsive to instantaneous increases in load, though it has the potential to start MP subtasks too frequently, thus incurring high wait, post, and address space dispatch costs.</p>		This parameter specifies the target number of threads on the MP offload queue per active task. Setting this parameter makes the <var class="product">Model 204</var> MP subtask scheduler more responsive to instantaneous increases in load, though it has the potential to start MP subtasks too frequently, thus incurring high wait, post, and address space dispatch costs.</p>
	<p>		<p>
	The default value of 2 means that if there are more than twice as many units of MP offloadable work waiting to be processed in an MP subtask as there are active subtasks, and fewer than <var>AMPSUBS</var> subtasks are currently running, another MP offload subtask is activated. </p>		The default value of 2 means that if there are more than twice as many units of MP offloadable work waiting to be processed in an MP subtask as there are active subtasks, and fewer than <var>[[AMPSUBS_parameter\|AMPSUBS]]</var> subtasks are currently running, another MP offload subtask is activated. </p>
	<p>		<p>
	<var>SCHDOFL</var> has no effect if either of these is true: </p>		<var>SCHDOFL</var> has no effect if either of these is true: </p>

DCameron: /* Summary */

2017-05-24T11:05:06Z

Summary

← Older revision		Revision as of 11:05, 24 May 2017
Line 9:		Line 9:
	<dd>On User 0's parameter line or reset by system manager.		<dd>On User 0's parameter line or reset by system manager.
	<dt>Related products		<dt>Related products
	<dd>~~All~~		<dd><var>[[MP/204#Multiprocessing_.28MP.2F204.29\|MP/204]]</var>
	<dt>Introduced		<dt>Introduced
	<dd><var class="product">Model 204 V7.4</var> ( was available in previous releases but wasn't documented )		<dd><var class="product">Model 204 V7.4</var> ( was available in previous releases but wasn't documented )

DCameron: /* Summary */

2017-05-24T10:51:42Z

Summary

← Older revision		Revision as of 10:51, 24 May 2017
Line 11:		Line 11:
	<dd>All		<dd>All
	<dt>Introduced		<dt>Introduced
	<dd><var class="product">Model 204 V7.4</var>		<dd><var class="product">Model 204 V7.4</var> ( was available in previous releases but wasn't documented )
	</dl>		</dl>

JAL: /* Description */ add `s`

2016-08-05T00:18:41Z

Description: add <var>s

← Older revision		Revision as of 00:18, 5 August 2016
Line 29:		Line 29:
	<var>[[SCHDOFLZ parameter\|SCHDOFLZ]]</var> performs the same function as <var>SCHDOFL</var> for zIIP (SRB) subtasks. <var>[[SCHDOFLS parameter\|SCHDOFLS]]</var> controls how aggressively MP subtasks are started to help out zIIP subtasks, and how aggressively MP subtasks take work from zIIP subtasks. </p>		<var>[[SCHDOFLZ parameter\|SCHDOFLZ]]</var> performs the same function as <var>SCHDOFL</var> for zIIP (SRB) subtasks. <var>[[SCHDOFLS parameter\|SCHDOFLS]]</var> controls how aggressively MP subtasks are started to help out zIIP subtasks, and how aggressively MP subtasks take work from zIIP subtasks. </p>
	<p>		<p>
	Before Model 204 7.7, the minimum allowed value for <var>SCHDOFL</var> is 1. Under Model 204 7.7 and later, it is 0, though it is probably a bad idea to set <var>SCHDOFL</var> to 0 unless the [[MPDELAY parameter]] is set to a non-zero value.		Before Model 204 7.7, the minimum allowed value for <var>SCHDOFL</var> is 1. Under Model 204 7.7 and later, it is 0, though it is probably a bad idea to set <var>SCHDOFL</var> to 0 unless the <var>[[MPDELAY parameter\|MPDELAY]]</var> parameter is set to a non-zero value.
	</p>		</p>

	[[Category:System parameters]]		[[Category:System parameters]]
	[[Category:Parameters]]		[[Category:Parameters]]

Alex: /* Description */

2016-08-02T05:29:57Z

Description

← Older revision		Revision as of 05:29, 2 August 2016
Line 28:		Line 28:
	<p>		<p>
	<var>[[SCHDOFLZ parameter\|SCHDOFLZ]]</var> performs the same function as <var>SCHDOFL</var> for zIIP (SRB) subtasks. <var>[[SCHDOFLS parameter\|SCHDOFLS]]</var> controls how aggressively MP subtasks are started to help out zIIP subtasks, and how aggressively MP subtasks take work from zIIP subtasks. </p>		<var>[[SCHDOFLZ parameter\|SCHDOFLZ]]</var> performs the same function as <var>SCHDOFL</var> for zIIP (SRB) subtasks. <var>[[SCHDOFLS parameter\|SCHDOFLS]]</var> controls how aggressively MP subtasks are started to help out zIIP subtasks, and how aggressively MP subtasks take work from zIIP subtasks. </p>
			<p>
			Before Model 204 7.7, the minimum allowed value for <var>SCHDOFL</var> is 1. Under Model 204 7.7 and later, it is 0, though it is probably a bad idea to set <var>SCHDOFL</var> to 0 unless the [[MPDELAY parameter]] is set to a non-zero value.
			</p>
	[[Category:System parameters]]		[[Category:System parameters]]
	[[Category:Parameters]]		[[Category:Parameters]]

JAL: /* Description */ minor formatting

2016-07-28T19:23:07Z

Description: minor formatting

← Older revision		Revision as of 19:23, 28 July 2016
Line 20:		Line 20:
	The default value of 2 means that if there are more than twice as many units of MP offloadable work waiting to be processed in an MP subtask as there are active subtasks, and fewer than <var>AMPSUBS</var> subtasks are currently running, another MP offload subtask is activated. </p>		The default value of 2 means that if there are more than twice as many units of MP offloadable work waiting to be processed in an MP subtask as there are active subtasks, and fewer than <var>AMPSUBS</var> subtasks are currently running, another MP offload subtask is activated. </p>
	<p>		<p>
	<var>SCHDOFL</var> has no effect if MP/204 is not in effect in an Online (<var>NMPSUBS</var> is 0) ~~or if the~~ number of active subtasks (<var>AMPSUBS</var>) is set to 0 or 1. (If <var>AMPSUBS</var> is 1, an MP subtask is activated as soon as there is any offloadable work and then runs until there is no more offloadable work for it to process.)</p>		<var>SCHDOFL</var> has no effect if either of these is true: </p>
			<ul>
			<li>MP/204 is not in effect in an Online (<var>NMPSUBS</var> is 0).</li>

			<li>The number of active subtasks (<var>AMPSUBS</var>) is set to 0 or 1. (If <var>AMPSUBS</var> is 1, an MP subtask is activated as soon as there is any offloadable work, and it then runs until there is no more offloadable work for it to process.)</li>
			</ul>
	<p>		<p>
	<var>[[SCHDOFLZ parameter\|SCHDOFLZ]]</var> performs the same function as <var>SCHDOFL</var> for zIIP (SRB) subtasks. <var>[[SCHDOFLS parameter\|SCHDOFLS]]</var> controls how aggressively MP subtasks are started to help zIIP subtasks ~~out~~, and how aggressively MP subtasks take work from zIIP subtasks. </p>		<var>[[SCHDOFLZ parameter\|SCHDOFLZ]]</var> performs the same function as <var>SCHDOFL</var> for zIIP (SRB) subtasks. <var>[[SCHDOFLS parameter\|SCHDOFLS]]</var> controls how aggressively MP subtasks are started to help out zIIP subtasks, and how aggressively MP subtasks take work from zIIP subtasks. </p>

	[[Category:System parameters]]		[[Category:System parameters]]
	[[Category:Parameters]]		[[Category:Parameters]]

JAL: minor cleanup

2016-07-28T19:00:03Z

minor cleanup

← Older revision		Revision as of 19:00, 28 July 2016
Line 16:		Line 16:
	==Description==		==Description==
	<p>		<p>
	This parameter specifies the target number of threads on the MP offload queue per active task. Setting this parameter makes the <var class="product">Model 204</var> MP subtask scheduler more responsive to instantaneous increases in load, though it has the potential ~~cost of starting~~ MP subtasks too frequently ~~and~~ incurring high wait, post, and address space dispatch costs.</p>		This parameter specifies the target number of threads on the MP offload queue per active task. Setting this parameter makes the <var class="product">Model 204</var> MP subtask scheduler more responsive to instantaneous increases in load, though it has the potential to start MP subtasks too frequently, thus incurring high wait, post, and address space dispatch costs.</p>
	<p>		<p>
	The default value of 2 means that if there are more than twice as many units of MP offloadable work waiting to be processed in an MP subtask as there are active subtasks, and fewer than <var>AMPSUBS</var> subtasks are currently running, another MP offload subtask is activated. </p>		The default value of 2 means that if there are more than twice as many units of MP offloadable work waiting to be processed in an MP subtask as there are active subtasks, and fewer than <var>AMPSUBS</var> subtasks are currently running, another MP offload subtask is activated. </p>

SCHDOFL parameter - Revision history

DCameron: /* Description */

DCameron: /* Description */

DCameron: /* Description */

DCameron: /* Description */

DCameron: /* Summary */

DCameron: /* Summary */

JAL: /* Description */ add s

Alex: /* Description */

JAL: /* Description */ minor formatting

JAL: minor cleanup

JAL: /* Description */ add `s`