 |
|
Oracle Database Tips by Donald Burleson |
Using Netstat to determine
SDU/TDU
SQL*Net tuning can be a challenging topic,
so it will not be covered extensively here. Oracle has many valuable
references including Document ID 1018693.6 How can SQL*Net
performance be improved, and 1005123.6 Tuning SQL*Net for better
performance. These should help if it is determined that there is a
network-related problem that needs to be tuned from Oracle.
Another way to get this information is to
communicate with the network group or system administration group.
Obtaining information this way helps keep communications open with
these groups, which is a good idea.
Regardless of the way the information is
obtained, make sure that these values are set correctly since having
the network use larger packet sizes will help performance. Since
every network packet has overhead; larger packets will result in
fewer packets, and therefore less network-related overhead. Unless
the packets are sized too large and they end up getting split up
which will create more network-related overhead, so be careful.
The last way to tune the network is reducing
the number and size of the database accesses. This boils down to
tuning SQL. By making efficient use of the database through
reducing unnecessary data requests; there will be less traffic, and
the remaining network traffic will get through with less delays.
There are important
things to consider when tuning the network. One of which is to only
work on it if the results from the wait analysis indicate that there
is a problem. Another very important item is that if tuning in this
arena is required, undertaking this alone as the DBA is not
recommended. Work with someone in the networking group to get an
understanding of the existing network configuration and what options
are available for changing it.
The above book excerpt is from:
Oracle Wait Event Tuning
High Performance with Wait
Event Iinterface Analysis
ISBN 0-9745993-7-9
Stephen Andert
http://www.rampant-books.com/book_2004_2_wait_tuning.htm |