The following table describes the tables and provides guidance about which ones to enable.
The shaded rows in the table below are the resource usage tables that are generally not used at customer sites.
|Table Name||Covers||When You Should Enable|
|ResUsageIpma||System-wide node information, intended primarily for Teradata engineers.||---|
|ResUsageIvpr||System-wide virtual processor information, intended primarily for Teradata engineers.||---|
|ResUsageSawt||Data specific to the AMP Worker Tasks.||When you want to monitor the utilization of the AMP Worker Task and determine if work is backing up because the AMP Worker Tasks are all being used.|
|ResUsageScpu||Statistics on the CPUs within the nodes.||When the performance analysis suggests that the overall performance is limited or to check if a program is spinning in an infinite loop on an individual processor.
For example, saturation of a particular CPU on each node or on a particular node while others are idle could indicate a task always uses that CPU.
Also, you should enable when the system is first brought online to verify the following:
|ResUsageShst||Statistics on the host channels and LANs that communicate with Teradata Database.||To determine details about the traffic over the IBM Host channels and if there is a bottleneck.|
|ResUsageSldv||System-wide, logical device statistics collected from the storage driver.||To observe the balance of disk usage. The storage device statistics are often difficult to interpret with disk arrays attached due to multi-path access to disks.
Use the ResUsageSvdsk table first to observe general system disk utilization unless specifically debugging at a low level.
|ResUsageSpdsk||Statistics collected from the pdisk device.||To obtain detailed usage information about pdisks.|
|ResUsageSpma||System-wide node information provides a summary of overall system utilization incorporating the essential information from most of the other tables.
Use the columns in ResUsageSpma to view BYNET utilization.
The BYNET can transmit and receive at the same time, resulting in 100% transmitting and 100% receiving values simultaneously.
Another method of determining BYNET utilization and traffic is to use the blmstat tool.
|To provide an overall history of the system operation.|
|ResUsageSps||Statistics based on the WD the work is being performed for.||When you need to track utilization by the WD level.|
|ResUsageSvpr||Data specific to each virtual processor and its file system.||To view details about the resources being used by each vproc on the system. This table is useful for looking for hot AMPS or PEs that may be CPU bound or throttled on other resources.|