Creating and Editing a Workload - Teradata Viewpoint

Teradata Viewpoint User Guide

Product
Teradata Viewpoint
Release Number
16.00
Published
October 2016
Language
English (United States)
Last Update
2018-03-29
dita:mapPath
fey1467302953244.ditamap
dita:ditavalPath
2206_User_vp_1600_NEW.ditaval.ditaval
dita:id
B035-2206
lifecycle
previous
Product Category
Analytical Ecosystem
You can group queries that share characteristics into a workload so that a set of workload management controls can be applied to the group. Different options are available in SLES 10 and SLES 11 systems:
SLES 10 TASM system
Uses an enforcement priority (EP) or a label to assign weights for the queries running in a workload.
SLES 11 system
Uses a workload management method or a label to assign access levels for the queries running in a workload.
  1. Edit or create a ruleset.
  2. From the ruleset toolbar, click Workloads.
  3. Next to Workloads, click .
  4. In the General tab, enter a name.
  5. [Optional] Enter a description.
  6. [Optional] On a SLES 11 TASM system, select a virtual partition to assign the workload. If only one virtual partition is available, it is selected by default.
  7. Under Enforcement Priority or Workload Management Method, select one of the following options for queries in this workload:
    Operating System Description
    SLES 10 (TASM for Enterprise Data Warehouse platforms only) Select an enforcement priority for the type of queries you expect to run in this workload.
    • Tactical queries are short, critical queries with defined service level goals. They are typically single or few-AMP queries or all-AMP queries that consume less than 1 CPU-second per node.
    • Priority queries are important and have higher priority than most other work.
    • Normal queries are the average priority work running on the system.
    • Background queries run for work that does not have a response-time requirement.
    SLES 11 (TASM for Enterprise Data Warehouse platforms only) Select a workload management method.
    • Tactical queries are short and high-priority. They have access to all available resources.
    • SLG Tier queries have access to the resources that remain after tactical resource demands are met. Multiple tiers can be prioritized so higher level tiers have higher resource allocation. SLG Tier workloads are assigned to the lowest available tier.
    • Timeshare queries have access to the resources that remain after tactical and SLG resource demands are met. Timeshare workloads are assigned to the Medium access level, but can be changed.
    SLES 11 IWM Select a workload management method.
    • Tactical queries are short and high-priority. They have access to all available resources.
    • Timeshare queries have access to the resources that remain after tactical resource demands are met. Timeshare workloads are assigned to the Medium access level, but can be changed.
  8. Click Save.
  9. [Optional] Click the Classification tab and add criteria to classify incoming queries into this workload.
  10. [Optional] Click the Throttles tab.
    1. Click on a state to set a throttle to limit concurrent queries classified into this workload. If you have a SLES 11 EDW system and are using Teradata Database 16.0 or later, you can designate that flex throttles be applied. See Enabling and Configuring Flex Throttles for more information.
    2. Select a group throttle from the list to make this workload a member of a workload group throttle.
  11. [Optional] On a SLES 11 TASM system, click the Service Level Goals tab and set service level goals for this workload.
  12. [Optional] Click the Exceptions tab and create an exception with criteria that trigger actions or notifications for this workload. For example, if a query in this workload is taking too long, create an exception that moves the query to a different workload.
  13. [Optional] In a SLES 11 tactical workload, click the Tactical Exception tab and modify the tactical exception.
  14. Click Save.