1. Just a point of clarity, in SLES 11 the allocation is to the workload, not a group of workloads as in SLES 10. To decide the appropriate allocation (aka share percent), look at peak CPU usage for the workload in SLES 10. Then make sure the allocation you give for the workload will allow it to get that level of resources in SLES 11.
To understand what level of node resources a workload will be offered when a workload is on SLG Tier 2, multiply the workload's allocatoin percent by the allocation of all parents in the hierarchy above that workload. In this case that would be the Remaining workload on SLG Tier 1 and the virtual partition allocation percent.
2. The limit of 20 on reserved AWTs is a Viewpoint convention, to prevent a user form over-allocation reserve pools for tactical at the expense of other active work. AWTs for the new reserve pools come from the general pool of unassigned AWTs. The reasoning is that if you are require more than 20 AWTs to be reserved, you are likely expediting non-tactical work, and the recommendation would be to un-expedite some of those workloads that may be of a less tatical nature.
3. Each query in Timeshare Top will get 8 times the resource of any query running in Timeshare Low, it doesn't matter what the concurrency levels are. No matter how few the queries in Top, they will always run more efficiently than the queries in Low. We recommend that you place workloads in Timeshare based on priority.
Why don't you wait and see how it actually works for you when you get on SLES 11. I would prefer not to get too deeply into hypothetical scenarios.
4. See the blog posting titled: Expedite Your Tactical Queries, Whether You Think They Need It or Not.
It would be a little easier for me to respond to comments if they could be kept down to 1 or 2 questions at a time. If you are seeking in depth knowledge on a topic, Teradata training classes, Teradata Education Network webinars, orange books, and official publications might be more suitable sources to turn to.
Thanks, -Carrie
1. Just a point of clarity, in SLES 11 the allocation is to the workload, not a group of workloads as in SLES 10. To decide the appropriate allocation (aka share percent), look at peak CPU usage for the workload in SLES 10. Then make sure the allocation you give for the workload will allow it to get that level of resources in SLES 11.
To understand what level of node resources a workload will be offered when a workload is on SLG Tier 2, multiply the workload's allocatoin percent by the allocation of all parents in the hierarchy above that workload. In this case that would be the Remaining workload on SLG Tier 1 and the virtual partition allocation percent.
2. The limit of 20 on reserved AWTs is a Viewpoint convention, to prevent a user form over-allocation reserve pools for tactical at the expense of other active work. AWTs for the new reserve pools come from the general pool of unassigned AWTs. The reasoning is that if you are require more than 20 AWTs to be reserved, you are likely expediting non-tactical work, and the recommendation would be to un-expedite some of those workloads that may be of a less tatical nature.
3. Each query in Timeshare Top will get 8 times the resource of any query running in Timeshare Low, it doesn't matter what the concurrency levels are. No matter how few the queries in Top, they will always run more efficiently than the queries in Low. We recommend that you place workloads in Timeshare based on priority.
Why don't you wait and see how it actually works for you when you get on SLES 11. I would prefer not to get too deeply into hypothetical scenarios.
4. See the blog posting titled: Expedite Your Tactical Queries, Whether You Think They Need It or Not.
It would be a little easier for me to respond to comments if they could be kept down to 1 or 2 questions at a time. If you are seeking in depth knowledge on a topic, Teradata training classes, Teradata Education Network webinars, orange books, and official publications might be more suitable sources to turn to.
Thanks, -Carrie