Think about the priority part of workload management for a minute.
The settings that the administrator makes when defining priorities for different workloads are on the surface--things like workload allocation percentages and access level assignments. They are easy to see. Below the surface are “global weights”, which starting in Teradata Database 14.10 indicate to you the actual percentage of platform resources your workload will receive, based on its allocation.
But they do more than translate your settings to an expected resource share. Global weights are used by the database to order the queues for several internal entities. For example, the AMP worker task (AWT) message queue is now ordered by global weight in SLES 11.
So it’s time you spent a few minutes taking a closer look at what global weights are, how the SLES 11 priority scheduler calculates them, and how you can influence them.