Minimum Response Time Characteristics | Teradata Vantage - Minimum Response Time Characteristics - Analytics Database - Teradata Workload Management

Teradata Vantageā„¢ - Workload Management User Guide - 17.20

Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
VMware
Product
Analytics Database
Teradata Workload Management
Release Number
17.20
Published
June 2022
Language
English (United States)
Last Update
2023-01-27
dita:mapPath
aji1628112479055.ditamap
dita:ditavalPath
qkf1628213546010.ditaval
dita:id
B035-1197
Product Category
Teradata Vantage
Note the following specifics about minimum response time:
  • TASM can hold responses from 1 to 3,600 seconds, and the value can vary by planned environment.
  • The minimum response time does not affect SET commands, EXEC commands, stored procedure calls, and transaction statements. For stored procedures, TASM does not hold the CALL statement, but it treats each statement in the procedure as a separate request. This means that each request can have a minimum response time if the request is in a workload with a minimum response time. This is also true for statements in a macro.
  • TASM places a request on hold at the point where the database would normally send the response to the client: AMP steps have completed, locks are released, and TASM throttle counters have been decremented.
  • The RESPONSE-HELD PE state, which is shown in the Viewpoint Workload Monitor portlet, indicates that a response is on hold. TASM can abort a request in the RESPONSE-HELD state. However, TASM cannot release a held request until the minimum response time expires.
  • Once the return of an answer set has been placed on hold, the minimum response time for the request does not change due to planned environment or rule set changes.