All Tactical workloads have an associated Tactical Exception that identifies and acts on requests that have non-Tactical characteristics. If a resource-intensive request starts to run in a Tactical workload, TASM demotes that request to another workload.
- Tactical CPU Time
- Tactical I/O Physical Byte
- CPU (sum over all nodes) in CPU seconds
- CPU per Node in CPU seconds
- I/O (sum over all nodes) in KB, MB, or GB
- I/O per Node in KB, MB, or GB
When a request exceeds a per node limit, the request is demoted on that one node only. When a request exceeds a sum over all nodes limit, the request is demoted across all nodes. It is possible that a request can exceed a per node limit on one or more AMPs but not exceed the sum over all nodes limit. In that case, the request could run in different workloads on different nodes. One way to keep requests running in the same workload on all nodes is to set the per node and sum across all nodes thresholds to the same value.
- CPU: TacticalCPUException
- I/O: TacticalIOException
By default, the sum over all nodes CPU and I/O thresholds are automatically set at the per node setting multiplied by the number of nodes in the system. To change this default, use the Tactical Exception tab on the Workloads view.