AGESLICE parameter: Difference between revisions
Jump to navigation
Jump to search
(Automatically generated page update) |
|||
| Line 18: | Line 18: | ||
<p>It is appropriate to increase AGESLICE when the values of AGESCAN or AGEINTVL are increased. Never set AGESLICE to a value greater than SLICEMAX. AGESLICE has no effect unless the AGESCAN parameter value is nonzero.</p> | <p>It is appropriate to increase AGESLICE when the values of AGESCAN or AGEINTVL are increased. Never set AGESLICE to a value greater than SLICEMAX. AGESLICE has no effect unless the AGESCAN parameter value is nonzero.</p> | ||
[[Category:Scheduler parameters]] | [[Category:Scheduler parameters]] | ||
[[Category:System | [[Category: System Parameters]] | ||
[[Category:Parameters]] | [[Category:Parameters]] | ||
Revision as of 15:48, 19 April 2013
Summary
- Default value
- 0
- 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 CPU time slice increment associated with aging promotion
This parameter is multiplied by the value of the multiplier and then added to the user's current CPU time slice allotment, subject to SLICEMAX. Increasing this parameter causes a user's CPU time slice immunity to increase faster with aging.
Although increasing AGESLICE increases a user's waiting time, it also allows a CPU-bound user more time once that user is running. This increases throughput but reduces response time.
It is appropriate to increase AGESLICE when the values of AGESCAN or AGEINTVL are increased. Never set AGESLICE to a value greater than SLICEMAX. AGESLICE has no effect unless the AGESCAN parameter value is nonzero.