Sizing | Teradata QueryGrid - QueryGrid Manager Sizing - Teradata QueryGrid

Teradata® QueryGrid™ Installation and User Guide
Product
Teradata QueryGrid
Release Number
2.19
Published
July 2022
Language
English (United States)
Last Update
2022-07-28
dita:mapPath
jpf1654813554544.ditamap
dita:ditavalPath
ft:empty
dita:id
lxg1591800469257
Product Category
Analytical Ecosystem
The following is a list of the minimum requirements for QueryGrid Manager to serve 200 data source nodes and monitor 5000 QueryGrid queries a day. A single QueryGrid Manager can support up to 8 CPUs total. QueryGrid Manager uses a maximum of 16GB of memory.
  • 2 CPU cores
  • 2.2GHz
  • 16GB memory
  • 250GB of disk space mounted on /var/opt/teradata/tdqgm

    Do not store /var/opt/teradata/tdqgm on the same partition as root.

Number of QueryGrid Manager Instances

For each Data Center, determine the number of QueryGrid Managers needed. One instance of QueryGrid Manager is installed on one TMS, customer-supplied server, or VM.

Use the following guidelines. The guidelines are based on the minimum hardware requirements for the TMS, server, or VM.

Requirements Description
TMS, Server, or VM for QueryGrid Manager One or more (separate server for each QueryGrid Manager instance).
Important: Do not install on existing TMS servers hosting Viewpoint, Data Mover, Ecosystem Manager, and so forth, unless those products are uninstalled and the server is re-purposed to be a QueryGrid Manager server.
Minimum number of QueryGrid Manager instances One instance for approximately every 200 Teradata QueryGrid-connected nodes:
  • This approximation is based on moderate query volume on minimum supported hardware requirements.
  • Actual required number varies depending on server specifications and query volume.
  • New QueryGrid Managers can be added if load is high on existing instances to reduce overall load.
Minimum number of QueryGrid Manager instances for high availability (HA) Two instances:
  • More than two instances can be deployed.
  • Multiple instances can be clustered for high availability and scalability.
  • Each instance in a cluster is fully active and maintains a full copy of the QueryGrid configuration.
Number of QueryGrid Manager instances to keep communication, heartbeats, query metrics, and log data local to a Data Center At least one per Data Center, more if the number of nodes in the Data Center exceed the resource requirements of the single QueryGrid Manager instance.

Server load is displayed by Linux utilities such as uptime and top. The load average should be less than the number of CPU cores. If the load is persistently above the number of CPU cores, that is a good indication that another QueryGrid Manager is needed.