In the following experiments. The NIC card connection has been changed. For a pure text version of this page, see here
------------------
| switch |
| |
| 10 9 11|
------------------
| | |
| | |
| | | 132.177.8.0/25
------------------- | -------------------
| | |
| | |
| | |
| | |
----------------- ------------------- ---------------------
| eth2 | | eth0 | | eth2 |
| | | | | |
| Madrid | | Dublin | | Prague |
| | | | | |
| eth0 eth1 | | eth2 eth1 | | eth1 eth0 |
----------------- ------------------- ---------------------
3.1| |1.2 1.1| |2.1 2.2 | | 3.2
| ----------------- ---------------- |
| 192.168.1.0/24 192.168.2.0/24 |
| |
--------------------------------------------------------
192.168.3.0/24eth0 is 3Com NIC card
eth1, eth2 are Tulip NIC card Re-do the four experiments Experiment 1: [lin@prague ttcp]$ ttcp -r -s ttcp-r: buflen=8192, nbuf=2048, align=16384/0, port=5001 tcp ttcp-r: socket ttcp-r: accept from 192.168.3.1 ttcp-r: 16777216 bytes in 1.43 real seconds = 11431.70 KB/sec +++ ttcp-r: 12281 I/O calls, msec/call = 0.12, calls/sec = 8568.89 ttcp-r: 0.0user 0.2sys 0:01real 18% 0i+0d 0maxrss 0+2pf 0+0csw [lin@madrid lin]$ ttcp/ttcp -t -s 192.168.3.2 < nttcp-1.47.tar.gz ttcp-t: buflen=8192, nbuf=2048, align=16384/0, port=5001 tcp -> 192.168.3.2 ttcp-t: socket ttcp-t: connect ttcp-t: 16777216 bytes in 1.43 real seconds = 11464.12 KB/sec +++ ttcp-t: 2048 I/O calls, msec/call = 0.71, calls/sec = 1433.02 ttcp-t: 0.0user 0.3sys 0:01real 27% 0i+0d 0maxrss 0+2pf 0+0csw ================================= Experiment 2: [lin@prague ttcp]$ ttcp -r -s ttcp-r: buflen=8192, nbuf=2048, align=16384/0, port=5001 tcp ttcp-r: socket ttcp-r: accept from 192.168.1.2 ttcp-r: 16777216 bytes in 92.09 real seconds = 177.90 KB/sec +++ ttcp-r: 5145 I/O calls, msec/call = 18.33, calls/sec = 55.87 ttcp-r: 0.0user 0.0sys 1:32real 0% 0i+0d 0maxrss 0+2pf 0+0csw [lin@madrid lin]$ ttcp/ttcp -t -s 192.168.2.2 < nttcp-1.47.tar.gz ttcp-t: buflen=8192, nbuf=2048, align=16384/0, port=5001 tcp -> 192.168.2.2 ttcp-t: socket ttcp-t: connect ttcp-t: 16777216 bytes in 91.84 real seconds = 178.40 KB/sec +++ ttcp-t: 2048 I/O calls, msec/call = 45.92, calls/sec = 22.30 ttcp-t: 0.0user 0.0sys 1:31real 0% 0i+0d 0maxrss 0+2pf 0+0csw ================================ Experiment 3: [lin@prague ttcp]$ ttcp -r -s ttcp-r: buflen=8192, nbuf=2048, align=16384/0, port=5001 tcp ttcp-r: socket ttcp-r: accept from 132.177.8.27 ttcp-r: 16777216 bytes in 74.65 real seconds = 219.47 KB/sec +++ ttcp-r: 5287 I/O calls, msec/call = 14.46, calls/sec = 70.82 ttcp-r: 0.0user 0.0sys 1:14real 0% 0i+0d 0maxrss 0+2pf 0+0csw [lin@madrid lin]$ ttcp/ttcp -t -s 132.177.8.29 < nttcp-1.47.tar.gz ttcp-t: buflen=8192, nbuf=2048, align=16384/0, port=5001 tcp -> 132.177.8.29 ttcp-t: socket ttcp-t: connect ttcp-t: 16777216 bytes in 74.20 real seconds = 220.80 KB/sec +++ ttcp-t: 2048 I/O calls, msec/call = 37.10, calls/sec = 27.60 ttcp-t: 0.0user 0.0sys 1:14real 0% 0i+0d 0maxrss 0+2pf 0+0csw From the experiment 1.
we do know that the onborad 3 Com NIC card is a little bit faster than PCI DECnet tulip card But why the LAN speed dramatically slow down. only about 1/50 of original speed. Is it because the LAN speed is slow tonight? Now it's 00:00am Oct 5th, 2001
To test the LAN speed. Switch to
original connection and test again.
NOTE: after you reboot, be sure the the static route on both madrid and prague
are set up well. Otherwise, it won't work.
================================
Experiment 1:
[lin@prague ttcp]$ ttcp -r -s
ttcp-r: buflen=8192, nbuf=2048, align=16384/0, port=5001 tcp
ttcp-r: socket
ttcp-r: accept from 192.168.3.1
ttcp-r: 16777216 bytes in 1.44 real seconds = 11406.25
KB/sec +++
ttcp-r: 12267 I/O calls, msec/call = 0.12, calls/sec = 8540.06
ttcp-r: 0.0user 0.1sys 0:01real 6% 0i+0d 0maxrss 0+2pf 0+0csw
[root@madrid lin]# ttcp/ttcp -t -s 192.168.3.2 <
nttcp-1.47
ttcp-t: buflen=8192, nbuf=2048, align=16384/0, port=5001 tcp ->
192.168.3.2ttcp-t: socket
ttcp-t: connect
ttcp-t: 16777216 bytes in 1.43 real seconds = 11461.03
KB/sec +++
ttcp-t: 2048 I/O calls, msec/call = 0.71, calls/sec = 1432.63
ttcp-t: 0.0user 0.0sys 0:01real 5% 0i+0d 0maxrss 0+2pf 0+0csw
=====================================
Experiment 2:
[lin@prague ttcp]$ ttcp -r -s
ttcp-r: buflen=8192, nbuf=2048, align=16384/0, port=5001 tcp
ttcp-r: socket
ttcp-r: accept from 192.168.1.2
ttcp-r: 16777216 bytes in 54.43 real seconds = 301.00
KB/sec +++
ttcp-r: 7539 I/O calls, msec/call = 7.39, calls/sec = 138.50
ttcp-r: 0.0user 0.0sys 0:54real 0% 0i+0d 0maxrss 0+2pf 0+0csw
[root@madrid lin]# ttcp/ttcp -t -s 192.168.2.2 <
nttcp-1.47
ttcp-t: buflen=8192, nbuf=2048, align=16384/0, port=5001 tcp ->
192.168.2.2ttcp-t: socket
ttcp-t: connect
ttcp-t: 16777216 bytes in 54.22 real seconds = 302.15
KB/sec +++
ttcp-t: 2048 I/O calls, msec/call = 27.11, calls/sec = 37.77
ttcp-t: 0.0user 0.0sys 0:54real 0% 0i+0d 0maxrss 0+2pf 0+0csw
=============================
Experiment 3
[lin@prague ttcp]$ ttcp -r -s
ttcp-r: buflen=8192, nbuf=2048, align=16384/0, port=5001 tcp
ttcp-r: socket
ttcp-r: accept from 132.177.8.27
ttcp-r: 16777216 bytes in 1.43 real seconds = 11430.92
KB/sec +++
ttcp-r: 12253 I/O calls, msec/call = 0.12, calls/sec = 8548.77
ttcp-r: 0.0user 0.2sys 0:01real 19% 0i+0d 0maxrss 0+2pf 0+0csw
[root@madrid lin]# ttcp/ttcp -t -s 132.177.8.29 <
nttcp-1.47
ttcp-t: buflen=8192, nbuf=2048, align=16384/0, port=5001 tcp -> 132.177.8.29
ttcp-t: socket
ttcp-t: connect
ttcp-t: 16777216 bytes in 1.43 real seconds = 11461.70
KB/sec +++
ttcp-t: 2048 I/O calls, msec/call = 0.71, calls/sec = 1432.71
ttcp-t: 0.0user 0.4sys 0:01real 34% 0i+0d 0maxrss 0+2pf 0+0csw
From the experiment 3, we see that the LAN speed is
still that fast. But why it was so slow when we use tulip card on it??????
