You can sort the records in any grid by clicking on the headers at the top of each column. Some grids have group boxes at the top, where appropriate, and some columns have a down arrow in a black box, which allows you to quickly filter grid records when you click it. You can rearrange columns by dragging with your mouse.
The Database tab displays information included in the database header page, plus additional information on memory allocations, the state of the sweep, etc. In future versions of IB Performance Monitor I plan to rearrange this tab so that you can see all information without scrolling.
There are two different modes available for the Memory tab: Graph and Grid. Choose which mode you'd like to use from the Monitor->Memory submenu. The grid gives more detailed information, but the graph shows a history of total memory consumption.
You may see the following Types of memory pools on the chart or grid. In the definitions below you will see the term request used frequently. A request is the compiled form of a query.
Note that IB Performance Monitor must update the memory view even when Memory is not the currently selected tab, if "Show Chart" is selected. All other tabs are updated only when they are selected, reducing the load on the server somewhat. For the lowest possible use of server resources when monitoring, choose "Show Grid."
You can zoom in on the History chart by clicking and dragging with the mouse.The grid displays a summarized view of the records InterBase returns. InterBase maintains a large number of memory pools; each is one of the seven types listed above.
Count is the number of pools of each type in the grid.
Extend amount is the amount by which an individual pool of a given type will be extended if the server needs more memory than is currently in that pool.
This tab displays information about resources consumed by procedures in the DB. A procedure will not appear on this list until it has been run by a user. The procedure will be dropped from the list when all users (including IB Performance Monitor) disconnect from the database.
A record for each SQL statements in use by the server is shown in the grid at the top of the tab. The SQL or DDL itself is shown for the currently selected record, with syntax highlighting, in the memo at the bottom of the tab.
The State column can have one of four values: ACTIVE, INACTIVE, STALLED, AND CANCELLED. STALLED means that the statement has executed, but the client has not fetched all rows yet; the server is waiting for the client to fetch the rest of the rows.
When the value in the State column for a statement is ACTIVE or STALLED, the "Cancel" button above the grid is enabled. Clicking this button will cancel the statement on the server, and the user running the statement will receive a "Statement cancelled" error (presuming that the statement didn't finish on its own in the time between when IB Performance Monitor read the table and the time when you clicked the "Cancel" button.
The "Memory" and "Quantum" columns show the amount of memory and CPU use for a particular statement, respectively.
Each table in the database is listed, along with information on the operations which users have performed on the table. You can exclude system tables (those tables whose names start with RDB$ or TMP$) by un-checking Monitor->Show System Tables on the main menu.
All transactions in use by the server in the currently selected database appear here. If the State is ACTIVE, you can commit or rollback the transaction by clicking on the buttons at the top of the grid.
All users connected to the currently selected database appear here. You can cancel a user's current operation or shut down their connection by clicking on the buttons at the top of the grid.