statspack advises

[mike2000]

Hi all,

Below is the results of my database:

Cache Sizes (end)
~~~~~~~~~~~~~~~~~
Buffer Cache: 44M Std Block Size: 8K
Shared Pool Size: 32M Log Buffer: 512K

Load Profile
~~~~~~~~~~~~ Per Second Per Transaction
--------------- ---------------
Redo size: 2,222.45 471,160.00
Logical reads: 27.83 5,900.00
Block changes: 3.24 686.00
Physical reads: 0.18 38.00
Physical writes: 0.19 41.00
User calls: 3.38 717.00
Parses: 0.91 193.00
Hard parses: 0.12 26.00
Sorts: 0.81 171.00
Logons: 0.00 0.00
Executes: 1.59 338.00
Transactions: 0.00

% Blocks changed per Read: 11.63 Recursive Call %: 67.11
Rollback per transaction %: 0.00 Rows per Sort: 52.64

Instance Efficiency Percentages (Target 100%)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Buffer Nowait %: 100.00 Redo NoWait %: 99.47
Buffer Hit %: 99.36 In-memory Sort %: 100.00
Library Hit %: 90.80 Soft Parse %: 86.53
Execute to Parse %: 42.90 Latch Hit %: 100.00
Parse CPU to Parse Elapsd %: 50.00 % Non-Parse CPU: 98.31

Shared Pool Statistics Begin End
------ ------
Memory Usage %: 89.76 91.24
% SQL with executions>1: 56.67 60.61
% Memory for SQL w/exec>1: 25.12 31.74

Top 5 Timed Events
~~~~~~~~~~~~~~~~~~ % Total
Event Waits Time (s) Ela Time
-------------------------------------------- ------------ ----------- --------
CPU time 1 77.22
control file parallel write 76 0 7.52
log file switch completion 2 0 4.52
control file sequential read 91 0 4.18
db file sequential read 40 0 2.71


What is the CPU time??? why the total time is high???? Is that b/c I don't have enough resource (CPU) on the server??? Beside that areas, what is the control files parralel areas ????

ANy others suggestions????

[sambavan]

CPU time is the time it takes to process the information. It could be result of the long running queires that are running on your system or due to other applications. The controlfile writes are mandetory, as the database keeps track of every thing on the control file. Like the last SCN and etc.

Sam