- PPId
- This field is obsolete and returns a value of zero.
- PGId
- This field returns the pWDid value.
- VprType
- Type of vproc:
- AMP
- PE
- MISC
- WDId
- WD ID. On SLES 11 or later systems, TASM Workloads rule is enabled. On SUSE Linux Enterprise Server 11 or later systems, TASM Workloads rule is enabled.
- AGId
- This field is obsolete and returns a value of zero.
- RelWgt
- This field is obsolete and returns a value of zero.
- NumProcs
- Average number of tasks of online nodes.
- QWaitTime
- Total wait time in milliseconds that work requests waited on an input queue before being serviced.
- QWaitTimeMax
- Maximum time in milliseconds that work requests waited on an input queue before being serviced.
- CPUUserPct
- Weighted average of CpuUserPct of each node.
- WorkMsgMaxDelay
- General indicator only. This field is result of the following calculation:
- WorkTypeInuseMax
- Total of the AMP Worker Task (AWT) columns:
- WorkTimeInuseAvg
- Average number of AWTs used. This field is result of:
- IODelay
- Number of I/Os that are delayed. This field is result of:
- IODelayTime
- Total time the I/O is delayed for. This field is the result of:
- PhysicalRead
- Number of physical reads performed for this period. This field is the result of:
- PhysicalReadKB
- Number of physical reads in KB performed for this period. This field is result of:
- PhysicalWrite
- Number of physical writes performed for this period. This field is result of:
- PhysicalWriteKB
- Number of physical writers in KB performed for this period. This field is result of:
- LogicalRead
- Number of logical reads performed for this period. This field is result of:
- LogicalReadKB
- Number of logical reads in KB performed for this period. This field is result of:
- LogicalWrite
- Number of logical writes performed for this period. This field is result of:
- LogicalWriteKB
- Number of logical writes in KB performed for this period. This field is result of:
- ExtraField1
- ExtraField2
- ExtraField3
- ExtraField4
- This field is not used.
- VPId
- Virtual partition ID.
- WaitIO
- Number of milliseconds tasks in WD waited for I/O over the reporting period.
- WaitOther
- Number of milliseconds tasks in WD waited for reasons other than I/O over the reporting period (for example, a task waiting for a message).
- CPURunDelay
- Number of milliseconds tasks in the WD sat in the CPU runqueue waiting to run over the reporting period.
- IOSubmitted
- Number of I/Os submitted on behalf of this WD.
- IOSubmittedKB
- KB of I/O submitted on behalf of this WD.
- IOCompleted
- Number of AgeOut Now data blocks not to keep in memory (fsgcache) and to be written to disk.
- IOCompletedKB
- KB of AgeOut Now data blocks not to keep in memory (fsgcache) and to be written to disk.
- IOCriticalSubmitted
- Number of I/Os submitted with critical status. These I/Os run at top priority instead of being based on the I/O priority of the SQL request.
- IOCriticalSubmittedKB
- KB of I/O submitted with critical status. These I/Os run at top priority instead of being based on the I/O priority of the SQL request.
- DecayLevel1IO
- Number of times SQL requests in the WD reached decay level 1 due to I/O.
- DecayLevel2IO
- Number of times SQL requests in the WD reached decay level 2 due to I/O.
- DecayLevel1CPU
- Number of times SQL requests in the WD reached decay level 1 due to CPU.
- DecayLevel2CPU
- Number of times SQL requests in the WD reached decay level 2 due to CPU.
- TacticalExceptionIO
- Number of times SQL requests in the WD reached a tactical per-node exception due to I/O.
- TacticalExceptionCPU
- Number of times SQL requests in the WD reached a tactical per-node exception due to CPU.
* The Workload Share Percent Management Method workload is assigned a proportion of the resources that are available after allocations have been made for tactical workloads. The percentage of resources is divided equally between all requests running in the WD. For example, if the Workload Share Percent is 5% and there are five SQL requests, each SQL request gets 1% of the share resources.
** The Timeshare Workload Management Method workload can be assigned to one of four stepped access levels, Top, High, Medium, or Low. The higher access levels are given larger access rates than the lower levels. For example, an SQL request assigned to a Timeshare WD with a Top access level, which has an access rate of 8, gets eight times the amount of resources than an SQL request assigned to a Low access level.
Timeshare workloads are assigned resources remaining after all allocations have been made for tactical and Workload Share Percent workloads.
*** The Tactical Workload Management Method workload yields the fastest available response time and runs at the highest tier, preempting all resource needs of other tiers. This method is well suited for critical, short-running queries that require fast response times.