- Top
- High
- Medium
- Low
How many resources a Timeshare tier request gets depends on the priority level of the workload it runs in. Higher-priority workloads receive more resources than lower-priority workloads.
Each priority level is assigned a rate, as follows.
| Timeshare Name | Rate |
|---|---|
| Top | 8 |
| High | 4 |
| Medium | 2 |
| Low | 1 |
These rates cannot be changed. The rate of 8 gives Top requests 8 times the resources as Low requests. High requests get 4 times the resources as Low requests, and Medium requests get 2 times the resources as Low requests. The number of requests in a Timeshare workload does not affect the rate. Even if you have only one request in Top and 10 in Low, Top requests still get 8 times the resources as Low requests.
Under normal situations, abundant resources flow down to Timeshare workloads. SLG tier workloads rarely need all the resources they are allocated. However, when critical work surges at the SLG tier level, SLG workloads may consume resources more fully, limited only by the allocation percentage set aside internally for Timeshare.
It is acceptable to give a Timeshare workload a different priority in different planned environments, for example, giving the Batch workload a Low priority in the Business_Hours planned environment and a Top priority in the Weekend planned environment. All of Timeshare is considered a single tier in the priority hierarchy.
- For simple implementations, you can achieve effective priority differences even without SLG tier workloads using the Top, High, Medium, and Low access levels.
- If you are not using SLG tiers, place workloads in Top if they are very high priority but do not qualify as tactical.
- Keep the Timeshare Decay option turned off for more predictable priority differentiation in Timeshare. For more information on the Timeshare Decay option, see Timeshare Decay.