WAITSCAN parameter: Difference between revisions
Jump to navigation
Jump to search
| (3 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
{{Template:WAITSCAN 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 real-time interval that is allowed to pass between wait queue checks</p> | <p>The real-time interval that is allowed to pass between wait queue checks</p> | ||
Latest revision as of 15:08, 6 December 2017
Wait scan interval
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 real-time interval that is allowed to pass between wait queue checks
WAITSCAN specifies the period in milliseconds at which lower priority CPU-bound users are preempted by higher priority users whose I/O has completed.
Decreasing this parameter reduces the time it takes for a lower priority user to get preempted, thus increasing the response differential between low and high priority users. However, decreasing this value also increases scheduler overhead. Because the effect on scheduler overhead is particularly strong, do not decrease the parameter without sufficient reason.
Increasing this parameter allows CPU-bound users to periodically lock out other users, reducing system throughput.