| AWR Report network foreground wait events [message #513875] |
Wed, 29 June 2011 16:59  |
 |
kavitagoel00
Messages: 5
Registered: June 2011
|
Junior Member |
|
|
I ran an AWR report. The database looks fine, but a data load that loaded 1 Million rows an hour is now doing 500K per hour.
Wait Class Waits %Time -outs Total Wait Time (s) Avg wait (ms) %DB time
DB CPU 224 80.70
Other 2,668 0 28 10 9.99
System I/O 4,753 0 9 2 3.23
Administrative 1 0 6 5543 2.00
Commit 357 0 4 11 1.46
User I/O 3,460 0 3 1 0.92
Network 630,601 0 1 0 0.24
Configuration 6 0 1 97 0.21
Application 65 0 0 5 0.12
Concurrency 20 0 0 0 0.00
The network value for wait: 630,601. What does this mean? Anything I should look at? When it was 1million per hour, the value was 4,563,000.
Top 5:
Top 5 Timed Foreground Events
Event Waits Time(s) Avg wait (ms) % DB time Wait Class
DB CPU 224 80.70
unspecified wait event 2,666 28 10 9.99 Other
control file sequential read 4,753 9 2 3.23 System I/O
switch logfile command 1 6 5543 2.00 Administrative
log file sync 357 4 11 1.46 Commit
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Re: AWR Report network foreground wait events [message #514034 is a reply to message #514011] |
Thu, 30 June 2011 15:53  |
|
kavitagoel00
Messages: 5
Registered: June 2011
|
Junior Member |
|
|
Thanks! I just want to know what the network waits mean? Is the database waiting? Is network taking that time to send packets? It doesnt seem to be in sec, milliseconds etc.? I just dont understand the number 4,552,760 and 630,601.
AWR report at 10AM:
Foreground Wait Class DB/Inst: APD1/apd1 Snaps: 19323-19325
-> s - second, ms - millisecond - 1000th of a second
-> ordered by wait time desc, waits desc
-> %Timeouts: value of 0 indicates value was < .5%. Value of null is truly 0
-> Captured Time accounts for 99.9% of Total DB time 1,582.65 (s)
-> Total FG Wait Time: 496.11 (s) DB CPU time: 1,085.56 (s)
Avg
%Time Total Wait wait
Wait Class Waits -outs Time (s) (ms) %DB time
-------------------- ---------------- ----- ---------------- -------- ---------
DB CPU 1,086 68.6
User I/O 89,528 0 450 5 28.4
System I/O 10,636 0 15 1 1.0
Other 1,309 0 14 11 0.9
Commit 387 0 8 20 0.5
Network 4,552,760 0 8 0 0.5
Configuration 12 0 1 60 0.0
Administrative 1 0 1 664 0.0
Application 75 0 1 7 0.0
Concurrency 4 0 0 0 0.0
-------------------------------------------------------------
AWR Report at 3 PM:
Foreground Wait Class DB/Inst: APD1/apd1 Snaps: 19333-19335
-> s - second, ms - millisecond - 1000th of a second
-> ordered by wait time desc, waits desc
-> %Timeouts: value of 0 indicates value was < .5%. Value of null is truly 0
-> Captured Time accounts for 98.9% of Total DB time 277.45 (s)
-> Total FG Wait Time: 50.41 (s) DB CPU time: 223.91 (s)
Avg
%Time Total Wait wait
Wait Class Waits -outs Time (s) (ms) %DB time
-------------------- ---------------- ----- ---------------- -------- ---------
DB CPU 224 80.7
Other 2,668 0 28 10 10.0
System I/O 4,753 0 9 2 3.2
Administrative 1 0 6 5543 2.0
Commit 357 0 4 11 1.5
User I/O 3,460 0 3 1 0.9
Network 630,601 0 1 0 0.2
Configuration 6 0 1 97 0.2
Application 65 0 0 5 0.1
Concurrency 20 0 0 0 0.0
-------------------------------------------------------------
|
|
|
|
| Re: AWR Report network foreground wait events [message #514037 is a reply to message #514034] |
Thu, 30 June 2011 17:15 |
 |
BlackSwan
Messages: 26766
Registered: January 2009
Location: SoCal
|
Senior Member |
|
|
>I just dont understand the number 4,552,760 and 630,601.
It is count or number of times this class of wait event happened; which is a 100% irrelevant number.
The number to care about is Total Wait Time (in seconds).
The 630,601 Network waits slowed down response time a total of 1 seconds out of 1 hour reporting period.
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
Anyway. Thanks for the help.