Performance monitor objects – Oracle A423961 User Manual

Page 87

Advertising
background image

4 – 3

Getting the Most out of Integration with Windows NT

Additional Information:

For more information on the

Performance Monitor, see your operating system
documentation.

Additional Information:

For more information on the meaning

of Windows NT Performance Monitor results, and what you can
do about your database performance, see Oracle7 Server Tuning
and your operating system documentation.

Performance Monitor Objects

Performance Monitor objects are detailed below.

Memory Allocation Objects

Object: Oracle7 Library Cache

The Library Cache object contains one counter, the reloads/pins
percentage counter.

This value is not time derived.

The reloads/pins is the percent of SQL statements, PL/SQL blocks and
object definitions which required re–parsing. This percentage should be
near ZERO. If the percentage is greater than 1%, then you should reduce
the library cache misses. See Reducing Library Cache Misses in Oracle7
Server Tuning
.

Object: Oracle7 Data Dictionary Cache

The Data Dictionary Cache object contains one counter, the get
misses/gets percentage counter.

This value is not time derived.

For frequently accessed dictionary caches, the value of this counter
should be less than 10–15%. If the ratio continues to increase above this
threshold while your application is running, increase the amount of
memory available to the data dictionary cache. See Reducing Data
Dictionary Cache Misses
in Oracle7 Server Tuning.

Object: Oracle7 Buffer Cache

The Buffer Cache object contains one counter, the phyreads/gets
percentage counter.

This value is not time derived.

If the Miss counter is high (higher than 30% – 40%), increase the number
of buffers in the cache to improve performance. See Reducing Buffer
Cache Misses
in Oracle7 Server Tuning.

Advertising