Memory Considerations | Teradata Vantage on VMware - Memory Considerations - Teradata Vantage on VMware

Teradata Vantageā„¢ on VMware Base, Advanced, Enterprise Tiers Getting Started Guide

Product
Teradata Vantage on VMware
Release Number
Deployer 3.04
Published
October 2021
Language
English (United States)
Last Update
2021-10-29
dita:mapPath
qbi1545241606156.ditamap
dita:ditavalPath
lyx1526581533412.ditaval
dita:id
B035-5958
Product Category
Cloud
Memory and CPU are reserved for each virtual machine. A Vantage system is a distributed system and cannot be load balanced with VMware DRS. Vantage functions as a parallel system, therefore performance is based on the speed of the slowest vnode. Each ESXi host requires CPU and memory to function, so an algorithm automatically attempts to ensure ESXi has enough to function. All systems are different, and at times the CPU and memory reservations set for Vantage nodes can be too high for some ESXi hosts. If this occurs, some virtual nodes will not boot, and the vSphere Client interface displays errors to indicate which reservation is too high. To resolve this issue, you can set override values in the common.IT.properties.json properties file.
  • For memory reservation, set the MemoryMBPerTPA property to be lower than the automatically calculated value.
  • For CPU reservation, set the EsxiCPUreserved property to be higher than the automatically calculated percentage.

The database image used by Vantage on VMware allows only 64 GB of memory for a crash dump. Higher memory amounts will not allow for a complete crash dump. A crash dump is used for debugging issues, and debugging of larger memory dumps is not supported at this time.