15.10 - Partition Assignments Overview - Teradata Database

Teradata Database Resource Usage Macros and Tables

Product
Teradata Database
Release Number
15.10
Published
April 2016
Language
English (United States)
Last Update
2018-05-17
dita:mapPath
Resource_Usage_Macros_15_10.ditamap
dita:ditavalPath
ft:empty
dita:id
resource_usage_macros_1099_v15.10

With regards to Teradata Database, there is more than one definition of partition. The partitions here refer to the following Parallel Database Extensions (PDE) and vproc definition:

  • A partition is a collection of tasks and associated resources grouped within a virtual processor according to the function of the tasks. There are multiple partitions within a single virtual processor. Partitions are the primary mechanism used by Teradata Database for managing parallel programs.
  • Partitions are the subdivision of vproc software processes into 48 semi-isolated domains.

For example, in an AMP vproc, Partition 11 is the AMP Worker Task Partition. In all other vproc types, Partition 11 is unused.

Another partition description is only meaningful in a dialog between client programs and Teradata Database. It has nothing to do with PDE vproc partitions, but is a way of enforcing rules about what a client session is allowed to do and of keeping client sessions isolated from each other. This concept of partitions is centered in the CLIv2 interface, specifically the CONNECT parcel.

Partition reservation is as follows:

  • Partitions 0 through 6 are reserved by PDE
  • Partitions 7 through 47 are for use by Teradata Database

The table listed under Partition Assignment Listing describes the individual partitions. Teradata Database uses the following vprocs:

Vproc Type Description
AMP Access module processors perform database functions, such as executing database queries. Each AMP owns a portion of the overall database storage.
GTW Gateway vprocs provide a socket interface to Teradata Database.
Node The node vproc handles PDE and operating system functions not directly related to AMP and PE work. Node vprocs cannot be externally manipulated, and do not appear in the output of the Vproc Manager utility.
PE Parsing engines perform session control, query parsing, security validation, query optimization, and query dispatch.
RSG Relay Services Gateway provides a socket interface for relaying dictionary changes to the Teradata Meta Data Services utility.
TVS Manages Teradata Database storage. AMPs acquire their portions of database storage through the TVS vproc.

For more information on partition usage, see Process Scheduling: CPU Utilization Columns.