Queue monitor

Deployment options: Netezza Performance Server for Cloud Pak for Data System

The Queue Monitor summarizes the short and long queues on the system and how busy they are. The report shows you the number of snippets in the snippet queues and the number of jobs in the GRA queues.

The current chart shows the values for the latest sample of data:
  • The number of long GRA jobs that are waiting for GRA resources.
  • The number of short GRA jobs that are waiting for GRA scheduler slots.
  • The number of long snippets that are waiting for resources.
  • The number of short snippets that are waiting for resources.

The Queue Sizes Monitor trend chart displays the recent history of these four queues. For newly added hosts, the charts show a short sample of trend, but the charts can grow to show up to six days of trend. You can use the zoom in and zoom out tool at the bottom of the panel to see a specific range such as the previous 8 hours. If the chart shows an unexpected or interesting change in the trend, you can drill down to take a closer look at the time frame and jump to the query history for that time frame.

Netezza Performance Server systems separate short queries (typically those queries that run in two seconds or less) from longer-running queries. For “lightly loaded” systems, the queues might be zero if no queries are waiting, or small. As the system becomes busy with concurrent short or long queries, these queues can show a larger number of waiting snippets and jobs.

Netezza Performance Server reserves resources specifically for short queries so that it can run and complete those short queries even while it is busy running longer queries.

For Netezza Performance Server for Cloud Pak for Data System 1.0.X, see also Managing workloads.

For Netezza Performance Server for Cloud Pak for Data System 2.0.X, see also Managing workloads.

For Netezza Performance Server for Cloud Pak for Data, see also Managing workloads.

This figure shows a sample Queue monitor.Queue monitor

The query that is used:
set timezone to gmt; select DATE_PART('epoch', current_timestamp) as timestamp, sn.sn_short, sn.sn_long, gra.gra_short, gra.gra_long from (select sum(plans_waiting_short) as sn_short, sum(plans_waiting_long) as sn_long from _v_sched_sn where entry_ts = (select max(entry_ts) from _v_sched_sn)) sn CROSS JOIN (select sum(plans_waiting_short) as gra_short, sum(plans_waiting_long) as gra_long from _v_sched_gra where entry_ts = (select max(entry_ts) from _v_sched_gra)) gra