Home » RDBMS Server » Performance Tuning » AWR Report network foreground wait events (11.1.0.7.0, Linux)
AWR Report network foreground wait events [message #513875] Wed, 29 June 2011 16:59 Go to next message
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 #513876 is a reply to message #513875] Wed, 29 June 2011 17:09 Go to previous messageGo to next message
BlackSwan
Messages: 26766
Registered: January 2009
Location: SoCal
Senior Member
It would be helpful if you followed Posting Guidelines - http://www.orafaq.com/forum/t/88153/0/

>Anything I should look at?
SQL_TRACE the data load session & post results from tkprof

[Updated on: Wed, 29 June 2011 17:11]

Report message to a moderator

Re: AWR Report network foreground wait events [message #514007 is a reply to message #513876] Thu, 30 June 2011 13:46 Go to previous messageGo to next message
kavitagoel00
Messages: 5
Registered: June 2011
Junior Member
I just want to know if the network wait is better if its high or low
Network 630,601 0 1 0 0.24

Re: AWR Report network foreground wait events [message #514008 is a reply to message #514007] Thu, 30 June 2011 13:48 Go to previous messageGo to next message
kavitagoel00
Messages: 5
Registered: June 2011
Junior Member
Sorry for not putting in formatted text. Here is better formatted text:


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 #514009 is a reply to message #514008] Thu, 30 June 2011 13:57 Go to previous messageGo to next message
BlackSwan
Messages: 26766
Registered: January 2009
Location: SoCal
Senior Member
>Sorry for not putting in formatted text. Here is better formatted text:
REALLY?

Network is responsible for less than 1% so even it went to ZERO you would likely not notice any gain from it.
Re: AWR Report network foreground wait events [message #514010 is a reply to message #514009] Thu, 30 June 2011 14:01 Go to previous messageGo to next message
kavitagoel00
Messages: 5
Registered: June 2011
Junior Member
Sorry, When I did copy paste, it was better. Sad Anyway. Thanks for the help.
Re: AWR Report network foreground wait events [message #514011 is a reply to message #514010] Thu, 30 June 2011 14:19 Go to previous messageGo to next message
Michel Cadot
Messages: 68659
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
kavitagoel00 wrote on Thu, 30 June 2011 21:01
Sorry, When I did copy paste, it was better. Sad Anyway. Thanks for the help.


Please read How to use [code] tags and make your code easier to read.
Make sure that lines do not exceed 80 characters when you format.
Use code tags and align the columns in result.
Use the "Preview Message" button to verify.

Regards
Michel

Re: AWR Report network foreground wait events [message #514034 is a reply to message #514011] Thu, 30 June 2011 15:53 Go to previous messageGo to next message
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 Go to previous message
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.
Previous Topic: Performance Issue
Next Topic: Oracle hash join
Goto Forum:
  


Current Time: Sun Jun 16 22:58:37 CDT 2024