These columns provide the general characteristics of the housekeeping columns.
|Column Name||Mode||Description||Data Type|
|GmtTime||n/a||Greenwich Mean Time is not affected by the Daylight Savings Time adjustments that occur twice a year.||FLOAT|
|CabinetID||n/a||The physical cabinet number of the node.||INTEGER|
|ModuleID||n/a||The physical module number of the node.||INTEGER|
|VprId||n/a||Identifies the AMP vproc.
In Summary Mode, the value of the AMP vproc ID is -1.
|NodeType||n/a||Type of node, representing the per node system family type.||CHAR(8)|
|Secs||n/a||Actual number of seconds in the log period represented by this row. Normally the same as NominalSecs, but can be different in three cases:
Useful for normalizing the count statistics contained in this row, for example, to a per-second measurement.
|CentiSecs||n/a||Number of centiseconds in the logging period. This column is useful when performing data calculations with small elapsed times where the difference between centisecond-based data and whole seconds results in a percentage error.||INTEGER|
|NominalSecs||n/a||Specified or nominal number of seconds in the logging period.||SMALLINT|
|SummaryFlag||n/a||Summarization status of this row. If the value is 'N,' the row is a non-summary row. If the value is 'S,' the row is a summary row.||CHAR(1)|
|Active||max||Controls whether or not the rows will be logged to the resource usage tables if Active Row Filter Mode is enabled.
If Active is set to a non-zero value, the row contains data columns.
If Active is set to a zero value, none of the data columns in the row have been updated during the logging period.
For example, if you enable Active Row Filter Mode, the rows that have a zero Active column value will not be logged to the resource usage tables.
|TheTimestamp||n/a||Number of seconds since midnight, January 1, 1970.
This column is useful for aligning data with the DBQL log.
|PM_COD_CPU||n/a||Platform Metering (PM) CPU Capacity On Demand (COD) value in one tenths of a percent. For example, a value of 500 represents a PM CPU COD value of 50.0%.
The value is set to 1000 if the PM CPU COD is disabled.
|PM_COD_IO||n/a||Platform Metering (PM) I/O Capacity On Demand (COD) value in whole percent. For example, a value of 50 represents a PM I/O COD value of 50.0%.
The value is set to 100 if the PM I/O COD is disabled.
|WM_COD_CPU||n/a||Workload Management (WM) CPU Capacity On Demand (COD) value in one tenths of a percent. For example, a value of 500 represents a WM CPU COD value of 50.0%.
The value is set to 1000 if the WM CPU COD is disabled.
|WM_COD_IO||n/a||Workload Management (WM) I/O Capacity On Demand (COD) value in whole percent. For example, a value of 50 represents a WM I/O COD value of 50.0%.
The value is set to 100 if the WM I/O COD is disabled.
|TIER_FACTOR||n/a||I/O performance limit placed on a core-reduced node. For example, a value of 75 represents an I/O limit of 75.0% placed before other COD values.
The field is sourced from tpanodep->tierfactor, which is derived from the /proc/tdmeter/tier_performance file. A value of 100 indicates that there is no I/O performance limit applied to the node.