SIOSLICE parameter: Difference between revisions
m (Automatically generated page update) |
|||
| (7 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
{{Template:SIOSLICE parameter subtitle}} | |||
==Summary== | ==Summary== | ||
<dl> | <dl> | ||
| Line 10: | Line 11: | ||
<dd>All | <dd>All | ||
<dt>Introduced | <dt>Introduced | ||
<dd><var class="product">Model 204 | <dd><var class="product">Model 204 V2.1</var> or earlier | ||
</dl> | </dl> | ||
==Description== | ==Description== | ||
<p>The server real-time slice allotment in milliseconds for non-CPU-bound users</p> | <p>The server real-time slice allotment in milliseconds for non-CPU-bound users</p> | ||
<p>This parameter controls the time a non-CPU-bound user is allowed to remain in a server area without performing any terminal I/O. It is used primarily when a lower priority user in a server is denied CPU time because of higher priority, CPU-bound users. The latter type might be waiting for a server and might be of sufficient priority to be run in a server.</p> | <p>This parameter controls the time a non-CPU-bound user is allowed to remain in a server area without performing any terminal I/O. It is used primarily when a lower <var>[[PRIORITY_parameter|priority]]</var> user in a server is denied CPU time because of higher priority, CPU-bound users. The latter type might be waiting for a server and might be of sufficient priority to be run in a server.</p> | ||
<p>Decreasing SIOSLICE might generate increased server I/O, but it offers better service to higher priority users when there are few servers or when <var class="product">Model 204</var> is being run on a heavily overloaded system. Increasing this parameter can lower server I/O, but at the same time it diminishes the response differential between low and high priority users. SIOSLICE must not be set to less than twice the value of IOSLICE.</p> | <p>Decreasing SIOSLICE might generate increased server I/O, but it offers better service to higher priority users when there are few servers or when <var class="product">Model 204</var> is being run on a heavily overloaded system. Increasing this parameter can lower server I/O, but at the same time it diminishes the response differential between low and high priority users. SIOSLICE must not be set to less than twice the value of <var>[[IOSLICE_parameter|IOSLICE]]</var>.</p> | ||
[[Category: Scheduler | [[Category:Scheduler parameters]] | ||
[[Category: System | [[Category:System parameters]] | ||
[[Category:Parameters]] | [[Category:Parameters]] | ||
Latest revision as of 13:42, 31 May 2017
Server slice - IO
Summary
- Default value
- 250
- Parameter type
- System
- Where set
- On User 0's parameter line or reset by system manager
- Related products
- All
- Introduced
- Model 204 V2.1 or earlier
Description
The server real-time slice allotment in milliseconds for non-CPU-bound users
This parameter controls the time a non-CPU-bound user is allowed to remain in a server area without performing any terminal I/O. It is used primarily when a lower priority user in a server is denied CPU time because of higher priority, CPU-bound users. The latter type might be waiting for a server and might be of sufficient priority to be run in a server.
Decreasing SIOSLICE might generate increased server I/O, but it offers better service to higher priority users when there are few servers or when Model 204 is being run on a heavily overloaded system. Increasing this parameter can lower server I/O, but at the same time it diminishes the response differential between low and high priority users. SIOSLICE must not be set to less than twice the value of IOSLICE.