Entering content frame

Background documentation Performance: Partitions (DB2 UDB for UNIX and Windows) Locate the document in its SAP Library structure

In multi-partition database systems this overview screen provides a selection of performance data that is related to each partition. You can use the information to identify performance-critical partitions before starting a more detailed analysis of your database.

You can access the Partition Overview screen by calling the DBA Cockpit and choosing Performance  ® Partitions in the navigation frame of the DBA Cockpit.

For each partition of your database system, the following information is displayed:

Column

Description

Partition

Number of the selected partition

No. Buffer Pools

Number of buffer pools used for a partition

Total Size Buffer Pools

Total size in KB of all buffer pools used for a partition

Data Logical Reads

Number of read accesses to data in the buffer pool

Index Logical Reads

Number of read accesses to index data in the buffer pool

Data Physical Reads

Number of read accesses to data on disk (I/O). The value includes the number of physical reads that were performed synchronously (by the database manager agents) and asynchronously (by the I/O servers).

Index Physical Reads

 

Number of read accesses to index data on disk (I/O). Since index data is read only by the database manager agents, this value includes the number of synchronously read index pages.

Avg. Phys. Read Time (ms)

 

Average time in milliseconds required to read data from disk into the buffer pool

Avg. Phys. Write Time (ms)

 

Average time in milliseconds required to write data from the buffer pool to disk

Executed SQL Statements

 

Number of executed SQL statements (SELECT, INSERT, UPDATE, DELETE)

Package Cache Size

 

Amount of application heap memory to be used for caching a package’s static and dynamic SQL statements. As of DB2 Version 5, each database agent accesses a global cache.

Package Cache Quality (%)

 

Tells you whether or not the package or catalog cache is being used effectively. If the hit ratio of the package or catalog cache is greater than 95%, the cache is performing well.

Note

If you double-click a line, database snapshot data is retrieved and displayed as described in Performance: Database Snapshot.


 

Leaving content frame