AGEINTVL parameter: Difference between revisions
(Automatically generated page update) |
|||
| (3 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
{{Template:AGEINTVL parameter subtitle}} | |||
==Summary== | ==Summary== | ||
<dl> | <dl> | ||
| Line 14: | Line 15: | ||
==Description== | ==Description== | ||
<p>The real-time interval in milliseconds a user must wait before being promoted by the aging feature</p> | <p>The real-time interval in milliseconds a user must wait before being promoted by the aging feature</p> | ||
<p>Because queues are not scanned faster than AGESCAN, a user might have to wait a multiple of AGEINTVL milliseconds before being noticed by the scheduler. In this case, the aging logic determines how many complete AGEINTVL intervals have passed while the user waited, and it remembers this multiplier. The priority and time slice increments, AGEINCR and AGESLICE, are then multiplied by this interval.</p> | <p>Because queues are not scanned faster than <var>[[AGESCAN_parameter|AGESCAN]]</var>, a user might have to wait a multiple of AGEINTVL milliseconds before being noticed by the scheduler. In this case, the aging logic determines how many complete AGEINTVL intervals have passed while the user waited, and it remembers this multiplier. The priority and time slice increments, <var>[[AGEINCR_parameter|AGEINCR]]</var> and <var>[[AGESLICE_parameter|AGESLICE]]</var>, are then multiplied by this interval.</p> | ||
<p>For example, suppose that AGESCAN=240000 (four minutes) and AGEINTVL=120000 (two minutes). Further, suppose that you start waiting for the CPU and shortly afterward an aging scan takes place. You have not waited two minutes, and thus are not aged. When the aging scan again takes place, you have waited slightly more than four minutes. The aging logic determines that you have waited two complete AGEINTVL intervals, and assigns you a multiplier of 2. This multiplier is then applied to AGEINCR and AGESLICE. </p> | <p>For example, suppose that AGESCAN=240000 (four minutes) and AGEINTVL=120000 (two minutes). Further, suppose that you start waiting for the CPU and shortly afterward an aging scan takes place. You have not waited two minutes, and thus are not aged. When the aging scan again takes place, you have waited slightly more than four minutes. The aging logic determines that you have waited two complete AGEINTVL intervals, and assigns you a multiplier of 2. This multiplier is then applied to AGEINCR and AGESLICE. </p> | ||
<p>AGEINTVL has no effect unless the AGESCAN parameter value is nonzero.</p> | <p>AGEINTVL has no effect unless the AGESCAN parameter value is nonzero.</p> | ||
Latest revision as of 12:42, 9 October 2014
Aging interval
Summary
- Default value
- 86400000
- Parameter type
- System
- Where set
- On User 0's parameter line or reset by system manager
- Related products
- All
- Introduced
- Model 204 V6.1 or earlier
Description
The real-time interval in milliseconds a user must wait before being promoted by the aging feature
Because queues are not scanned faster than AGESCAN, a user might have to wait a multiple of AGEINTVL milliseconds before being noticed by the scheduler. In this case, the aging logic determines how many complete AGEINTVL intervals have passed while the user waited, and it remembers this multiplier. The priority and time slice increments, AGEINCR and AGESLICE, are then multiplied by this interval.
For example, suppose that AGESCAN=240000 (four minutes) and AGEINTVL=120000 (two minutes). Further, suppose that you start waiting for the CPU and shortly afterward an aging scan takes place. You have not waited two minutes, and thus are not aged. When the aging scan again takes place, you have waited slightly more than four minutes. The aging logic determines that you have waited two complete AGEINTVL intervals, and assigns you a multiplier of 2. This multiplier is then applied to AGEINCR and AGESLICE.
AGEINTVL has no effect unless the AGESCAN parameter value is nonzero.