Oracle网络性能诊断误区(tnsping/ping/ftp)

 

a. "I'm using TNSPING to test my network performance and..."

TNSPING should never be used to test network performance. TNSPING's only function is to send a Connect Packet (NSPTCN) to the listener; the listener replies with a Refuse Packet (NSPTRF) and a round trip time is computed. A slow TNSPING time could be anything from poor DNS resolution to a slow network to a busy listener to a busy server.

b. "SQL*Net query performance is slow but TCP/IP PING is fast, therefore SQL*Net is slow."

This is a false statement. Ping only uses the ICMP/IP protocol (not the TCP protocol) to test whether another host is reachable. Since the TCP protocol is not used, a socket is not created, therefore data is not transferred between 2 nodes (except for 8+[optional] bytes needed for the echo request, but again, that is not TCP data), and none of the rules of TCP are being applied. If Ping is fast, that only means that IP was able to quickly find a route to the destination server.

c. "PING is fast but TNSPING is slow. What is wrong with TNSPING?"

PING and TNSPING should not be used for ANY comparison. Please see "a" and "b" for explanations of TNSPING and PING

d. "Why are FTP/sftp transfers faster than sqlnet?"

Like PING, this test is not a good benchmark. There are no RFC standards for setting window sizes in FTP. The vendor may have FTP tuned very well with respect to window sizes. You are able to pass send and receive window sizes to TCP via sqlnet.

来自 “ ITPUB博客 ” ，链接：http://blog.itpub.net/14130873/viewspace-625179/，如需转载，请注明出处，否则将追究法律责任。

转载于:http://blog.itpub.net/14130873/viewspace-625179/