UIOSLIC parameter: Difference between revisions

From m204wiki
Jump to navigation Jump to search
(Automatically generated page update)
m (minor formatting)
 
(6 intermediate revisions by 2 users not shown)
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.1</var>
</dl>
</dl>
==Description==
==Description==
<p>The CPU time slice allotment, in milliseconds, for non-CPU-bound users</p>
<p>
<p>This parameter determines which requests are considered CPU-bound. A user request is considered IO-bound unless UIOSLIC milliseconds pass without the request voluntarily yielding the CPU. After UIOSLIC milliseconds, the user is considered CPU-bound. From this point, if UCPUSLIC milliseconds expire without yielding the CPU, the user is time sliced (forced to yield the CPU to the user with the next highest priority). </p>
The CPU time slice allotment, in milliseconds, for non-CPU-bound users</p>
<p>A user voluntarily yields the CPU by any of the following actions: </p>
<p>
This parameter determines which requests are considered CPU-bound. A user request is considered IO-bound unless <var>UIOSLIC</var> milliseconds pass without the request voluntarily yielding the CPU. After <var>UIOSLIC</var> milliseconds, the user is considered CPU-bound. From this point, if <var>[[UCPUSLIC parameter|UCPUSLIC]]</var> milliseconds expire without yielding the CPU, the user is time sliced (forced to yield the CPU to the user with the next highest priority). </p>
<p>
A user voluntarily yields the CPU by any of the following actions: </p>
<ul>
<ul>
<li>
<li>Executing a <var>[[Full-screen feature#READ SCREEN statement|READ SCREEN]]</var>, <var>[[Full-screen feature#READ MENU statement|READ MENU]]</var>, or <var>[[$Read]]</var> statement </li>
Executing a READ SCREEN, READ MENU, or $READ statement</li>
 
<li>
<li>Requesting I/O to a <var class="product">Model&nbsp;204</var> file or external sequential file</li>
Requesting I/O to a <var class="product">Model&nbsp;204</var> file or external sequential file</li>
 
<li>
<li>Going into a wait for a record or resource lock</li>
Going into a wait for a record or resource lock</li>
</ul>
</ul>
<p>Decreasing IOSLICE causes more requests to be considered CPU-bound, and increasing it causes fewer requests to be classed as CPU-bound. </p>
<p>
<p>Increasing this parameter diminishes the impact of dynamic dispatching, thus allowing CPU-bound requests to monopolize the CPU. Decreasing this parameter heightens the effect of dynamic dispatching, resulting in increased scheduler overhead.  </p>
Decreasing <var>IOSLICE</var> causes more requests to be considered CPU-bound, and increasing it causes fewer requests to be classed as CPU-bound. </p>
<p>For more information about <var class="product">Model&nbsp;204</var> dynamic dispatching, see the <var>Model&nbsp;204 System Manager's Guide</var>. </p>
<p>
Increasing this parameter diminishes the impact of dynamic dispatching, thus allowing CPU-bound requests to monopolize the CPU. Decreasing this parameter heightens the effect of dynamic dispatching, resulting in increased scheduler overhead.  </p>
<p>
For more information about <var class="product">Model&nbsp;204</var> dynamic dispatching, see [[Controlling system operations (CCAIN)#Dynamic dispatching|Dynamic dispatching]]. </p>
 
[[Category:Scheduler parameters]]
[[Category:Scheduler parameters]]
[[Category:System parameters]]
[[Category:System parameters]]
[[Category:Parameters]]
[[Category:Parameters]]

Latest revision as of 19:34, 16 October 2017

User I/O slice

Summary

Default value
30
Parameter type
System
Where set
On user's parameter line by system manager
Related products
All
Introduced
Model 204 V7.1

Description

The CPU time slice allotment, in milliseconds, for non-CPU-bound users

This parameter determines which requests are considered CPU-bound. A user request is considered IO-bound unless UIOSLIC milliseconds pass without the request voluntarily yielding the CPU. After UIOSLIC milliseconds, the user is considered CPU-bound. From this point, if UCPUSLIC milliseconds expire without yielding the CPU, the user is time sliced (forced to yield the CPU to the user with the next highest priority).

A user voluntarily yields the CPU by any of the following actions:

  • Executing a READ SCREEN, READ MENU, or $Read statement
  • Requesting I/O to a Model 204 file or external sequential file
  • Going into a wait for a record or resource lock

Decreasing IOSLICE causes more requests to be considered CPU-bound, and increasing it causes fewer requests to be classed as CPU-bound.

Increasing this parameter diminishes the impact of dynamic dispatching, thus allowing CPU-bound requests to monopolize the CPU. Decreasing this parameter heightens the effect of dynamic dispatching, resulting in increased scheduler overhead.

For more information about Model 204 dynamic dispatching, see Dynamic dispatching.