Gateway and Vproc Limits - Teradata Vantage

Teradata® VantageCloud Lake
Deployment
VantageCloud
Edition
Lake
Product
Teradata Vantage
Published
January 2023
ft:locale
en-US
ft:lastEdition
2024-12-11
dita:mapPath
phg1621910019905.ditamap
dita:ditavalPath
pny1626732985837.ditaval
dita:id
phg1621910019905
Parameter Value
Maximum number of sessions per PE. Multiple.

This is true because the gateway runs in its own vproc on each node.

The exact number depends on whether the gateways belong to different host groups and listen on different IP addresses.
Maximum number of sessions per gateway. Tunable: 1 - 2,147,483,647.

1,200 maximum certified.

The default is 600.
30,720
This includes the sum of all of the following types of vproc for a configuration:
  • AMP

    Access Module Processor vprocs

  • GTW

    Gateway Control vprocs

  • PE

    Parsing Engine vprocs

  • RSG

    Relay Services Gateway vprocs

  • TVS

    Teradata Virtual
Maximum number of AMP vprocs per system. 16,200
Maximum number of GTW vprocs per system.

This is a soft limit that Teradata Support personnel can reconfigure for you.

Each GTW vproc on a node must be in a different host group.

 The default is one GTW vproc per node with all GTW vprocs assigned to the same host group.
The maximum depends on the following:
  • Number of IP addresses assigned to each node.
  • Number of host groups configured in the database.

Each gateway on a node must be assigned to a different host group from any other gateway on the same node and each gateway must be assigned a disjoint set of IP addresses to service.

This does not mean all gateways in a system must be assigned to a different host group, but that each gateway on the same node must be assigned to a different host group.

Gateways on different nodes can be assigned to the same host group.
Maximum number of PE vprocs per system.

This is a soft limit that Teradata Support personnel can reconfigure for you.

 2,048
Maximum number of TVS allocator vprocs per system.

This is a soft limit that Teradata Support personnel can reconfigure for you.

 2,048
Maximum number of vprocs, in any combination, per node. 127
Maximum number of AMP vprocs per compute cluster. 8
Maximum number of external routine protected mode platform tasks per PE or AMP.

This value is derived by subtracting 1 from the maximum total of PE and AMP vprocs per system (because each system must have at least one PE), which is 16,384. This is obviously not a practical configuration.

The valid range is 0 to 20, inclusive. The limit is 20 platform tasks for each platform type, not 20 combined for both.

 20
Maximum number of external routine secure mode platform tasks per PE or AMP.

This value is derived by subtracting 1 from the maximum total of PE and AMP vprocs per system (because each system must have at least one PE), which is 16,384. This is obviously not a practical configuration.

 20
Size of a request control block ~ 40 bytes
Default number of lock segments per AMP vproc. 2
Maximum number of lock segments per AMP vproc. 8
Default size of a lock segment. 64 KB
Maximum size of a lock segment. 1 MB
Default number of locks per AMP 3,200
Maximum number of locks per AMP. 209.000
Maximum size of the lock table per AMP.

The AMP lock table size is fixed at 2 MB and cannot be altered.

 2 MB
Maximum size of the queue table FIFO runtime cache per PE.
  • 100 queue table entries
  • 1 MB
Maximum number of SELECT AND CONSUME requests that can be in a delayed state per PE. 24
Amount of private disk swap space required per protected or secure mode server for C/C++ external routines per PE or AMP vproc. 256 KB
Amount of private disk swap space required per protected or secure mode server for Java external routines per node. 30 MB