You should be aware of the rate at which your PM/API client application requests performance data. If a PM/API client application requests data more frequently than the corresponding data collection rate, an individual request could potentially include data from one collection period mixed in with data from a subsequent collection period initiated by a different MONITOR user because common global data is shared.
However, the impact need not be detrimental. The data collected from one request when compared with the next request may not show a change in resource usage. Follow the simple rule that the PM/API client application must request data at the same rate, or a less frequent rate, than the rate at which the Teradata Database collects that data.
The monitoring rate is a PM/API collection rate that sets the interval in seconds at which resource usage data is collected within memory.
Note: A physical monitoring rate is the same as a virtual monitoring rate.
There are significant differences in the way resource usage and session utilization data are collected and reported by the MONITOR partition. For details, see “Data Collection” on page 39 and “Collection and Logging Rates” on page 37.