Displays configured maximum parallelism level, count of queries started during the previous minute, and mean threads per query.

The warning (-w) and critical (-c) thresholds are applied to the query with the lowest parallelism level; if that level is below the warning threshold, then a warning alert is raised. If the level is below the critical threshold, a critical alert is raised. Note that critical threshold value should be less than the warning value. For more information, see Service Statuses.

The detail section displays statistics for queries started during each of the preceding 5 minutes, most current first. The table consists of 8 buckets ranging from 1 to the maximum configured parallelism level, and the value is a count of queries started with that number of threads. In the following example, for the third minute of the current hour:

214 queries were started with 29–32 threads per query in boldface

 15 queries were started with 21–24 threads per query

 89 queries were started with 17–20 threads per query

 31 queries were started with 13–16 threads per query

At query start time the scheduler determines parallelism level by looking at the number of currently executing queries and number of threads per query. If those values are relatively low, then the current query is likely to execute at or near max parallelism level. As those values increase, new queries will execute at lower and lower parallelism levels. A heavily loaded environment will tend to have most queries executing at the lower ranges of parallelism.