UCPUSLIC parameter: Difference between revisions
(Automatically generated page update) |
m (minor formatting) |
||
| (6 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
{{Template:UCPUSLIC parameter subtitle}} | |||
==Summary== | ==Summary== | ||
<dl> | <dl> | ||
| Line 6: | Line 7: | ||
<dd>System | <dd>System | ||
<dt>Where set | <dt>Where set | ||
<dd>On user's parameter line | <dd>On user's parameter line | ||
<dt>Related products | <dt>Related products | ||
<dd>All | <dd>All | ||
<dt>Introduced | <dt>Introduced | ||
<dd><var class="product">Model 204 V7. | <dd><var class="product">Model 204 V7.1</var> | ||
</dl> | </dl> | ||
==Description== | ==Description== | ||
<p>CPU milliseconds allowed while user is CPU bound.</p> | <p> | ||
<p>If a CPU-bound user does not yield the CPU voluntarily after UCPUSLIC milliseconds, the user is time sliced, that is, forced to yield the CPU to the user with the next highest priority. </p> | CPU milliseconds allowed while user is CPU bound.</p> | ||
<p>CPU-bound users that voluntarily yield the CPU are again considered IO-bound.</p> | <p> | ||
<p>Increasing this parameter results in improved service for CPU bound requests and reduced service for other requests. A smaller value for this parameter increases the rate at which a CPU-bound request falls in priority, resulting in poorer service for the request. </p> | If a CPU-bound user does not yield the CPU voluntarily after <var>UCPUSLIC</var> milliseconds, the user is time sliced, that is, forced to yield the CPU to the user with the next highest priority. </p> | ||
<p>Although a small value for this parameter improves service for non-CPU-bound requests, it can also reduce overall system throughput and performance by increasing scheduler overhead.</p> | <p> | ||
CPU-bound users that voluntarily yield the CPU are again considered IO-bound.</p> | |||
<p> | |||
Increasing this parameter results in improved service for CPU bound requests and reduced service for other requests. A smaller value for this parameter increases the rate at which a CPU-bound request falls in priority, resulting in poorer service for the request. </p> | |||
<p> | |||
Although a small value for this parameter improves service for non-CPU-bound requests, it can also reduce overall system throughput and performance by increasing scheduler overhead.</p> | |||
[[Category:Scheduler parameters]] | [[Category:Scheduler parameters]] | ||
[[Category:System parameters]] | [[Category:System parameters]] | ||
[[Category:Parameters]] | [[Category:Parameters]] | ||
Latest revision as of 19:32, 16 October 2017
User CPU slice
Summary
- Default value
- 10
- Parameter type
- System
- Where set
- On user's parameter line
- Related products
- All
- Introduced
- Model 204 V7.1
Description
CPU milliseconds allowed while user is CPU bound.
If a CPU-bound user does not yield the CPU voluntarily after UCPUSLIC milliseconds, the user is time sliced, that is, forced to yield the CPU to the user with the next highest priority.
CPU-bound users that voluntarily yield the CPU are again considered IO-bound.
Increasing this parameter results in improved service for CPU bound requests and reduced service for other requests. A smaller value for this parameter increases the rate at which a CPU-bound request falls in priority, resulting in poorer service for the request.
Although a small value for this parameter improves service for non-CPU-bound requests, it can also reduce overall system throughput and performance by increasing scheduler overhead.