Deployer 3.01 - Memory Considerations - Teradata Database on VMware

Teradata Database on VMware Base, Advanced, Enterprise Tiers Getting Started Guide

Teradata Database on VMware
Deployer 3.01
January 2018
CPU and memory are reserved for each virtual instance. A Teradata Database system is a distributed system and cannot be load balanced or the performance is reduced to the slowest virtual node. 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 the Teradata Database 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 properties file. For more information about using the following properties, see Additional Properties for Customization.
  • 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 Teradata Database on VMware allows only 64GB 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.