Ingres® 2006 - Interactive Performance Monitor User Guide

Peter Kitson

ISBN : -

Order a printed copy of this book from Amazon --UNAVAILABLE--


Cover Design - Ingres® 2006 - Interactive Performance Monitor User Guide
  

For your free electronic copy of this book please verify the numbers below. 

(We need to do this to make sure you're a person and not a malicious script)

Numbers

 



Sample Chapter From Ingres® 2006 - Interactive Performance Monitor User Guide
     Copyright © Ingres Corporation



Chapter 1: Introducing Ingres Performance Monitoring


The Interactive Performance Monitor User Guide provides a comprehensive look at the performance monitoring capabilities of Ingres®. This chapter provides a brief introduction to the Interactive Performance Monitor (IPM) and the ways it can be used. This chapter also introduces you to various conventions and notations used throughout the guide.

Interactive Performance Monitor

The Interactive Performance Monitor (IPM) monitors a running Ingres installation. It displays information about servers, sessions, and locking and logging activity.
IPM is an interactive, forms-based interface with the functionality of the following tools:

  • iimonitor
  • lockstat
  • logstat
  • iinamu

IPM can be used for multiple purposes, as follows:

Monitoring
IPM monitors the state of the different processes, the logging and locking systems, the database servers, the log file, and the user sessions.

Performance analysis
IPM can be used to analyze performance problems. It displays in real time which tables and pages are locked, whether the locks are shared or exclusive, and which transactions are blocking or possibly deadlocked with other transactions. It displays user sessions and whether each is active or waiting for user input, and displays log file and logging system statistics.

System management
IPM provides information useful for maintaining and tuning the Ingres configuration. For example, it displays in real time how much of the log file is in use and by whom. IPM can also be used to spot user behaviors that interfere with other users, such as transactions that are neither committed nor rolled back over a long time.