Greenplum Performance Monitor, an optional feature of Greenplum Database used to collect, store, and analyze system and query performance metrics.

Greenplum Performance Monitor allows administrators to collect query and system performance metrics from a running Greenplum Database system. Monitor data is stored within Greenplum Database. The Greenplum Performance Monitor Console (a graphical web application) can optionally be installed and used to view the collected performance monitor data.

Greenplum Performance Monitor is comprised of data collection agents that run on the master host and each segment host. The agents collect performance data about active queries and system utilization and send it to the Greenplum master at regular intervals. The data is stored in a dedicated database on the master, where it can be accessed through the Greenplum Performance Monitor Console or through SQL queries

 

 

The collection of query and system performance metrics is an optional feature of Greenplum Database that can be enabled or disabled using the gp_enable_gpperfmon server configuration parameter. Once enabled, the Greenplum Performance Monitor data collection agents run on all Greenplum Database hosts (master and segments), and are started and stopped along with the Greenplum Database server processes. The master agent polls all segment agents for performance data at a configurable interval (known as the quantum). The master agent pulls together the data from all segments, stores it in flat files, and periodically commits the data in the files to the Greenplum Performance Monitor database.

 
Greenplum Performance Monitor Database

The Greenplum Performance Monitor database (gpperfmon) is a database within your Greenplum system dedicated to storing and serving performance data. Your Greenplum Database installation includes setup scripts to install the gpperfmon database.

Greenplum administrators can connect to the monitor database using client programs such as psql or application programming interfaces (APIs) such as JDBC and ODBC. Administrators can also use the Greenplum Performance Monitor console to view reports on current and historical performance.

The database consists of three sets of tables

 

1. now tables store data on currently active queries,

2. history tables store data on completed queries, and

3. tail tables are for data in transition.

 

The now and tail data are stored as text files on the master file system, and accessed by Greenplum Database via external tables.

 

 

Greenplum administrators can connect to the monitor database using client programs such as psql or application programming interfaces (APIs) such as JDBC and ODBC. Administrators can also use the Greenplum Performance Monitor console to view reports on current and historical performance.

 

Setting Up Greenplum Performance Monitor
Installing and enabling Greenplum Performance Monitor is a two-part process.

1.Creating the Greenplum Performance Monitor database and enable Greenplum Performance Monitor data collection agents within Greenplum Database.

2. Install and configure the Greenplum Performance Monitor Console. (the Web application used to view the performance monitor data stored in Greenplum Database). The Greenplum Performance Monitor Console is shipped separately from your Greenplum Database installation. This step is optional as you can directly query the gpperfmon database using client programs such as psql or application programming interfaces (APIs) such as JDBC and ODBC.

We will discuss about,

1. Enabling the Performance Monitor Data Collection Agents
2. Installing the Greenplum Performance Monitor Console
3. Querying the Performance Monitor Database
4. Uninstalling Greenplum Performance Monitor