Hi,
We use dual 3.06 GHz Xeon PC servers, with 1 GB memory, 133-MHz/64-bit
PCI-X bus, and Intel PRO/10GbE 10-GigE NIC, as 10-GigE network performance
measurement and troubleshooting systems. With the 2.6.12.6 kernel we
get consistently excellent network performance, both TCP and UDP.
Here's a sample of the UDP performance, first transmitting from our
system chance (192.168.88.10) to our system chance4 (192.168.88.8),
followed by a transfer in the opposite direction.
chance% nuttcp -u -w5m 192.168.88.8
6348.3594 MB / 10.00 sec = 5322.9641 Mbps 99 %TX 66 %RX 0 / 812590 drop/pkt 0.
00 %loss
chance% nuttcp -u -r -w5m 192.168.88.8
6509.0312 MB / 10.00 sec = 5457.7234 Mbps 99 %TX 62 %RX 0 / 833156 drop/pkt 0.
00 %loss
As you can see, we get over 5 Gbps with zero packet drops which demonstrates
the network path is clean. The TCP performance is also excellent:
chance% nuttcp -w2m 192.168.88.8
6489.5625 MB / 10.00 sec = 5442.5464 Mbps 99 %TX 76 %RX
chance% nuttcp -r -w2m 192.168.88.8
6114.1250 MB / 10.00 sec = 5127.3559 Mbps 99 %TX 70 %RX
If we do the same tests on a 2.6.14.3 kernel, the UDP performance is still
excellent:
chance% nuttcp -u -w5m 192.168.88.8
6743.2656 MB / 10.02 sec = 5644.6505 Mbps 100 %TX 69 %RX 0 / 863138 drop/pkt 0
.00 %loss
chance% nuttcp -u -r -w5m 192.168.88.8
6692.6094 MB / 10.02 sec = 5602.4222 Mbps 100 %TX 69 %RX 0 / 856654 drop/pkt 0
.00 %loss
But the TCP performance is consistently 40% or more less than the
performance with the 2.6.12.6 kernel:
chance% nuttcp -w2m 192.168.88.8
3680.4890 MB / 10.02 sec = 3082.0133 Mbps 43 %TX 43 %RX
chance% nuttcp -r -w2m 192.168.88.8
3495.4405 MB / 10.02 sec = 2925.3573 Mbps 40 %TX 40 %RX
It appears that it is getting CPU starved for some reason (note the
43%/40% transmitter CPU usage versus the 99%/99% CPU usage for the
2.6.12.6 case).
If we use multiple streams, we can then get up to the maximum performance
level, first a sample with 2 streams:
chance% nuttcp -Is1 -w2m 192.168.88.8 & nuttcp -Is2 -w2m -p5002 192.168.88.8
s1: 2996.8977 MB / 10.02 sec = 2508.4744 Mbps 32 %TX 35 %RX
s2: 1795.0000 MB / 10.02 sec = 1502.0434 Mbps 26 %TX 24 %RX
That's an aggregate of 4010.5178 Mbps. And with 3 streams:
chance% nuttcp -Is1 -w2m 192.168.88.8 & nuttcp -Is2 -w2m -p5002 192.168.88.8 & n
uttcp -Is3 -w2m -p5003 192.168.88.8
s1: 3183.1493 MB / 10.02 sec = 2665.1879 Mbps 67 %TX 44 %RX
s2: 1583.1875 MB / 10.04 sec = 1322.9457 Mbps 27 %TX 26 %RX
s3: 1581.6250 MB / 10.04 sec = 1321.7448 Mbps 29 %TX 26 %RX
That's an aggregate of 5309.8784 Mbps which is comparable to the TCP
performance of the single stream 2.6.12.6 case.
I also tried testing with a 2.6.13.4 kernel. It gives inconsistent
results, sometimes slightly less than the 2.6.12.6 kernel such as:
chance% nuttcp -w2m 192.168.88.8
5848.0000 MB / 10.01 sec = 4900.5697 Mbps 96 %TX 67 %RX
chance% nuttcp -r -w2m 192.168.88.8
5817.9375 MB / 10.01 sec = 4875.8281 Mbps 91 %TX 71 %RX
And sometimes as bad as the 2.6.14.3 kernel:
chance% nuttcp -w2m 192.168.88.8
3627.4375 MB / 10.02 sec = 3037.6242 Mbps 44 %TX 47 %RX
chance% nuttcp -r -w2m 192.168.88.8
4149.6250 MB / 10.01 sec = 3477.6491 Mbps 54 %TX 52 %RX
The full network performance tests are attached below. They were
run from a script shortly after chance and chance4 were rebooted.
There was a 5 second sleep between each pair of tests, and there
were 10 pairs of TCP tests plus a UDP pair in each run.
The 2.6.13.4 kernel config was generated from the 2.6.12.6 config
by doing a "make oldconfig". Likewise the 2.6.14.3 config was
generated from the 2.6.13.4 config by doing a "make oldconfig" Here's
the diff between the different kernel versions (chance3 is another
system where the kernels were built):
[EMAIL PROTECTED] grep ^CONFIG /usr/src/linux-2.6.12.6/.config | sort >
/tmp/config-2.6.12
[EMAIL PROTECTED] grep ^CONFIG /usr/src/linux-2.6.13.4/.config | sort >
/tmp/config-2.6.13
[EMAIL PROTECTED] grep ^CONFIG /usr/src/linux-2.6.14.3/.config | sort >
/tmp/config-2.6.14
[EMAIL PROTECTED] diff /tmp/config-2.6.12 /tmp/config-2.6.13
37a38
> CONFIG_ASK_IP_FIB_HASH=y
274a276,278
> CONFIG_FLATMEM_MANUAL=y
> CONFIG_FLATMEM=y
> CONFIG_FLAT_NODE_MEM_MAP=y
279,282d282
< CONFIG_FUSION_CTL=m
< CONFIG_FUSION_LAN=m
< CONFIG_FUSION=m
< CONFIG_FUSION_MAX_SGE=40
285d284
< CONFIG_GAMEPORT_CS461X=m
291d289
< CONFIG_GAMEPORT_VORTEX=m
315a314,316
> CONFIG_HWMON=y
> CONFIG_HZ=100
> CONFIG_HZ_100=y
381a383
> CONFIG_INOTIFY=y
422a425
> CONFIG_IP_FIB_HASH=y
632a636
> CONFIG_NET_EMATCH_TEXT=m
668a673
> CONFIG_NFS_COMMON=y
763a769
> CONFIG_PHYSICAL_START=0x100000
775a782
> CONFIG_PREEMPT_NONE=y
863a871
> CONFIG_SELECT_MEMORY_MODEL=y
866d873
< CONFIG_SERIAL_8250_MULTIPORT=y
958a966
> CONFIG_TCP_CONG_BIC=y
959a968,970
> CONFIG_TEXTSEARCH_FSM=m
> CONFIG_TEXTSEARCH_KMP=m
> CONFIG_TEXTSEARCH=y
1011c1022
< CONFIG_USB_MON=m
---
> CONFIG_USB_MON=y
[EMAIL PROTECTED] diff /tmp/config-2.6.13 /tmp/config-2.6.14
36a37
> CONFIG_ARCH_MAY_HAVE_PC_FDC=y
155a157
> CONFIG_CHELSIO_T1=m
190a193
> CONFIG_DETECT_SOFTLOCKUP=y
294a298
> CONFIG_GENERIC_PENDING_IRQ=y
300d303
< CONFIG_HAVE_DEC_LOCK=y
329d331
< CONFIG_I2C_ISA=m
376a379
> CONFIG_INET_DIAG=y
378a382
> CONFIG_INET_TCP_DIAG=y
418a423
> CONFIG_IP6_NF_TARGET_HL=m
420a426,427
> CONFIG_IP6_NF_TARGET_NFQUEUE=m
> CONFIG_IP6_NF_TARGET_REJECT=m
443a451
> CONFIG_IP_NF_MATCH_CONNBYTES=m
445a454
> CONFIG_IP_NF_MATCH_DCCP=m
462a472
> CONFIG_IP_NF_MATCH_STRING=m
483a494
> CONFIG_IP_NF_TARGET_NFQUEUE=m
489a501
> CONFIG_IP_NF_TARGET_TTL=m
497,498d508
< CONFIG_IP_TCPDIAG_IPV6=y
< CONFIG_IP_TCPDIAG=m
567a578
> CONFIG_LOCALVERSION_AUTO=y
762d772
< CONFIG_PCI_NAMES=y
871a882
> CONFIG_SEMAPHORE_SLEEPERS=y
901a913
> CONFIG_SND_AC97_BUS=m
909c921
< CONFIG_SND_GENERIC_PM=y
---
> CONFIG_SND_GENERIC_DRIVER=y
926a939
> CONFIG_SND_SEQ_RTCTIMER_DEFAULT=y
967a981
> CONFIG_TEXTSEARCH_BM=m
994,995d1007
< CONFIG_USB_ALI_M5632=y
< CONFIG_USB_AN2720=y
998,999d1009
< CONFIG_USB_ARMLINUX=y
< CONFIG_USB_AUDIO=m
1001,1002d1010
< CONFIG_USB_AX8817X=y
< CONFIG_USB_BELKIN=y
1004d1011
< CONFIG_USB_CDCETHER=y
1009d1015
< CONFIG_USB_EPSON2888=y
1011d1016
< CONFIG_USB_GENESYS=y
1018d1022
< CONFIG_USB_KC2190=y
1023c1027,1030
< CONFIG_USB_NET1080=y
---
> CONFIG_USB_NET_AX8817X=m
> CONFIG_USB_NET_CDCETHER=m
> CONFIG_USB_NET_NET1080=m
> CONFIG_USB_NET_ZAURUS=m
1028d1034
< CONFIG_USB_PL2301=y
1066d1071
< CONFIG_USB_ZAURUS=y
Any ideas or a possible fix for this major TCP performance degradation
going from a 2.6.12.6 kernel to a 2.6.14.3 kernel?
-Thanks
-Bill
P.S. I've also attached the full 2.6.12.6 kernel config I'm using.
2.6.12.6 network performance test:
--------------------------------------------------------------------------------
chance% ping -c 5 -s 8972 192.168.88.8
PING 192.168.88.8 (192.168.88.8) from 192.168.88.10 : 8972(9000) bytes of data.
8980 bytes from 192.168.88.8: icmp_seq=1 ttl=64 time=1.09 ms
8980 bytes from 192.168.88.8: icmp_seq=2 ttl=64 time=1.00 ms
8980 bytes from 192.168.88.8: icmp_seq=3 ttl=64 time=0.991 ms
8980 bytes from 192.168.88.8: icmp_seq=4 ttl=64 time=0.996 ms
8980 bytes from 192.168.88.8: icmp_seq=5 ttl=64 time=0.989 ms
--- 192.168.88.8 ping statistics ---
5 packets transmitted, 5 received, 0% loss, time 4003ms
rtt min/avg/max/mdev = 0.989/1.015/1.093/0.039 ms
[using 9000 byte jumbo frames across an approximately 1 ms RTT network]
chance% nuttcp -xt 192.168.88.8
traceroute to 192.168.88.8 (192.168.88.8), 30 hops max, 38 byte packets
1 192.168.88.8 (192.168.88.8) 0.977 ms 0.942 ms 0.931 ms
traceroute to 192.168.88.10 (192.168.88.10), 30 hops max, 38 byte packets
1 192.168.88.10 (192.168.88.10) 0.980 ms 0.943 ms 0.994 ms
[shows it's a direct single hop L2 network path]
chance% nuttcp -u -w5m 192.168.88.8
6348.3594 MB / 10.00 sec = 5322.9641 Mbps 99 %TX 66 %RX 0 / 812590 drop/pkt
0.00 %loss
chance% nuttcp -u -r -w5m 192.168.88.8
6509.0312 MB / 10.00 sec = 5457.7234 Mbps 99 %TX 62 %RX 0 / 833156 drop/pkt
0.00 %loss
[UDP performance is excellent - over 5 Gbps with zero drops so network
path is clean]
chance% nuttcp -w2m 192.168.88.8
6489.5625 MB / 10.00 sec = 5442.5464 Mbps 99 %TX 76 %RX
chance% nuttcp -r -w2m 192.168.88.8
6114.1250 MB / 10.00 sec = 5127.3559 Mbps 99 %TX 70 %RX
[5 second sleeps between pairs of tests]
chance% nuttcp -w2m 192.168.88.8
6774.5625 MB / 10.00 sec = 5681.2952 Mbps 99 %TX 83 %RX
chance% nuttcp -r -w2m 192.168.88.8
6595.5625 MB / 10.00 sec = 5531.2145 Mbps 99 %TX 78 %RX
chance% nuttcp -w2m 192.168.88.8
6371.3750 MB / 10.00 sec = 5343.3748 Mbps 99 %TX 77 %RX
chance% nuttcp -r -w2m 192.168.88.8
6363.8125 MB / 10.00 sec = 5336.7998 Mbps 99 %TX 75 %RX
chance% nuttcp -w2m 192.168.88.8
6414.3125 MB / 10.00 sec = 5379.3420 Mbps 99 %TX 78 %RX
chance% nuttcp -r -w2m 192.168.88.8
6108.7500 MB / 10.00 sec = 5122.9652 Mbps 99 %TX 70 %RX
chance% nuttcp -w2m 192.168.88.8
6366.5625 MB / 10.00 sec = 5339.2331 Mbps 99 %TX 78 %RX
chance% nuttcp -r -w2m 192.168.88.8
6733.6875 MB / 10.01 sec = 5644.7277 Mbps 99 %TX 85 %RX
chance% nuttcp -w2m 192.168.88.8
6423.0000 MB / 10.00 sec = 5386.5830 Mbps 99 %TX 82 %RX
chance% nuttcp -r -w2m 192.168.88.8
6115.3750 MB / 10.00 sec = 5128.5114 Mbps 99 %TX 70 %RX
chance% nuttcp -w2m 192.168.88.8
6285.6875 MB / 10.00 sec = 5271.9512 Mbps 99 %TX 76 %RX
chance% nuttcp -r -w2m 192.168.88.8
6175.4375 MB / 10.00 sec = 5178.8130 Mbps 99 %TX 70 %RX
chance% nuttcp -w2m 192.168.88.8
6773.3750 MB / 10.00 sec = 5680.7599 Mbps 99 %TX 87 %RX
chance% nuttcp -r -w2m 192.168.88.8
6381.8750 MB / 10.00 sec = 5352.4894 Mbps 99 %TX 82 %RX
chance% nuttcp -w2m 192.168.88.8
6457.0625 MB / 10.00 sec = 5415.1449 Mbps 99 %TX 78 %RX
chance% nuttcp -r -w2m 192.168.88.8
6068.8125 MB / 10.00 sec = 5089.3977 Mbps 97 %TX 69 %RX
chance% nuttcp -w2m 192.168.88.8
6287.2500 MB / 10.00 sec = 5272.6981 Mbps 99 %TX 77 %RX
chance% nuttcp -r -w2m 192.168.88.8
6704.7500 MB / 10.00 sec = 5622.6938 Mbps 99 %TX 80 %RX
[TCP performance is consistently excellent - over 5 Gbps]
[average TCP performance is 5367 Mbps]
--------------------------------------------------------------------------------
2.6.13.4 network performance test:
--------------------------------------------------------------------------------
chance% ping -c 5 -s 8972 192.168.88.8
PING 192.168.88.8 (192.168.88.8) from 192.168.88.10 : 8972(9000) bytes of data.
8980 bytes from 192.168.88.8: icmp_seq=1 ttl=64 time=1.08 ms
8980 bytes from 192.168.88.8: icmp_seq=2 ttl=64 time=0.985 ms
8980 bytes from 192.168.88.8: icmp_seq=3 ttl=64 time=0.996 ms
8980 bytes from 192.168.88.8: icmp_seq=4 ttl=64 time=0.990 ms
8980 bytes from 192.168.88.8: icmp_seq=5 ttl=64 time=0.995 ms
--- 192.168.88.8 ping statistics ---
5 packets transmitted, 5 received, 0% loss, time 4047ms
rtt min/avg/max/mdev = 0.985/1.010/1.085/0.042 ms
chance% nuttcp -xt 192.168.88.8
traceroute to 192.168.88.8 (192.168.88.8), 30 hops max, 38 byte packets
1 192.168.88.8 (192.168.88.8) 0.956 ms 0.938 ms 0.930 ms
traceroute to 192.168.88.10 (192.168.88.10), 30 hops max, 38 byte packets
1 192.168.88.10 (192.168.88.10) 0.983 ms 0.941 ms 0.924 ms
chance% nuttcp -u -w5m 192.168.88.8
6736.2969 MB / 10.02 sec = 5638.8813 Mbps 100 %TX 69 %RX 0 / 862246 drop/pkt
0.00 %loss
chance% nuttcp -u -r -w5m 192.168.88.8
6734.0391 MB / 10.03 sec = 5631.8951 Mbps 100 %TX 69 %RX 0 / 861957 drop/pkt
0.00 %loss
[UDP performance is still excellent - over 5 Gbps with zero drops]
chance% nuttcp -w2m 192.168.88.8
3979.1250 MB / 10.01 sec = 3334.4508 Mbps 50 %TX 48 %RX
chance% nuttcp -r -w2m 192.168.88.8
5127.0625 MB / 10.01 sec = 4296.8334 Mbps 76 %TX 61 %RX
chance% nuttcp -w2m 192.168.88.8
5848.0000 MB / 10.01 sec = 4900.5697 Mbps 96 %TX 67 %RX
chance% nuttcp -r -w2m 192.168.88.8
5817.9375 MB / 10.01 sec = 4875.8281 Mbps 91 %TX 71 %RX
chance% nuttcp -w2m 192.168.88.8
3627.4375 MB / 10.02 sec = 3037.6242 Mbps 44 %TX 47 %RX
chance% nuttcp -r -w2m 192.168.88.8
4149.6250 MB / 10.01 sec = 3477.6491 Mbps 54 %TX 52 %RX
chance% nuttcp -w2m 192.168.88.8
3648.8980 MB / 10.02 sec = 3055.0085 Mbps 44 %TX 45 %RX
chance% nuttcp -r -w2m 192.168.88.8
5706.8125 MB / 10.01 sec = 4782.7633 Mbps 89 %TX 68 %RX
chance% nuttcp -w2m 192.168.88.8
5695.2500 MB / 10.01 sec = 4772.6028 Mbps 88 %TX 69 %RX
chance% nuttcp -r -w2m 192.168.88.8
5743.1250 MB / 10.02 sec = 4808.3945 Mbps 88 %TX 69 %RX
chance% nuttcp -w2m 192.168.88.8
6106.1250 MB / 10.02 sec = 5111.7834 Mbps 96 %TX 70 %RX
chance% nuttcp -r -w2m 192.168.88.8
5923.0000 MB / 10.01 sec = 4963.8950 Mbps 94 %TX 78 %RX
chance% nuttcp -w2m 192.168.88.8
3664.2500 MB / 10.03 sec = 3065.2745 Mbps 43 %TX 51 %RX
chance% nuttcp -r -w2m 192.168.88.8
5980.8125 MB / 10.01 sec = 5012.3595 Mbps 94 %TX 68 %RX
chance% nuttcp -w2m 192.168.88.8
5964.1875 MB / 10.02 sec = 4992.9395 Mbps 93 %TX 74 %RX
chance% nuttcp -r -w2m 192.168.88.8
3692.2500 MB / 10.02 sec = 3092.1903 Mbps 43 %TX 48 %RX
chance% nuttcp -w2m 192.168.88.8
5894.5625 MB / 10.01 sec = 4939.5970 Mbps 91 %TX 69 %RX
chance% nuttcp -r -w2m 192.168.88.8
5903.4375 MB / 10.01 sec = 4947.4242 Mbps 92 %TX 67 %RX
chance% nuttcp -w2m 192.168.88.8
3940.8750 MB / 10.01 sec = 3302.4246 Mbps 50 %TX 50 %RX
chance% nuttcp -r -w2m 192.168.88.8
3696.3271 MB / 10.03 sec = 3092.4557 Mbps 43 %TX 42 %RX
[TCP performance is highly erratic - ranging from a poor low of 3 Gbps
to a high slightly over 5 Gbps]
[average TCP performance is 4193 Mbps]
--------------------------------------------------------------------------------
2.6.14.3 network performance test:
--------------------------------------------------------------------------------
chance% ping -c 5 -s 8972 192.168.88.8
PING 192.168.88.8 (192.168.88.8) from 192.168.88.10 : 8972(9000) bytes of data.
8980 bytes from 192.168.88.8: icmp_seq=1 ttl=64 time=1.07 ms
8980 bytes from 192.168.88.8: icmp_seq=2 ttl=64 time=1.00 ms
8980 bytes from 192.168.88.8: icmp_seq=3 ttl=64 time=0.992 ms
8980 bytes from 192.168.88.8: icmp_seq=4 ttl=64 time=0.996 ms
8980 bytes from 192.168.88.8: icmp_seq=5 ttl=64 time=0.989 ms
--- 192.168.88.8 ping statistics ---
5 packets transmitted, 5 received, 0% loss, time 4037ms
rtt min/avg/max/mdev = 0.989/1.011/1.076/0.043 ms
chance% nuttcp -xt 192.168.88.8
traceroute to 192.168.88.8 (192.168.88.8), 30 hops max, 38 byte packets
1 192.168.88.8 (192.168.88.8) 0.972 ms 0.956 ms 0.942 ms
traceroute to 192.168.88.10 (192.168.88.10), 30 hops max, 38 byte packets
1 192.168.88.10 (192.168.88.10) 0.948 ms 0.904 ms 0.892 ms
chance% nuttcp -u -w5m 192.168.88.8
6743.2656 MB / 10.02 sec = 5644.6505 Mbps 100 %TX 69 %RX 0 / 863138 drop/pkt
0.00 %loss
chance% nuttcp -u -r -w5m 192.168.88.8
6692.6094 MB / 10.02 sec = 5602.4222 Mbps 100 %TX 69 %RX 0 / 856654 drop/pkt
0.00 %loss
[UDP performance is still excellent - over 5 Gbps with zero drops]
chance% nuttcp -w2m 192.168.88.8
3680.4890 MB / 10.02 sec = 3082.0133 Mbps 43 %TX 43 %RX
chance% nuttcp -r -w2m 192.168.88.8
3495.4405 MB / 10.02 sec = 2925.3573 Mbps 40 %TX 40 %RX
chance% nuttcp -w2m 192.168.88.8
3652.6250 MB / 10.02 sec = 3058.4986 Mbps 43 %TX 42 %RX
chance% nuttcp -r -w2m 192.168.88.8
3631.3750 MB / 10.02 sec = 3040.9977 Mbps 42 %TX 50 %RX
chance% nuttcp -w2m 192.168.88.8
3645.1860 MB / 10.02 sec = 3052.2132 Mbps 42 %TX 47 %RX
chance% nuttcp -r -w2m 192.168.88.8
3658.8651 MB / 10.02 sec = 3063.3938 Mbps 43 %TX 44 %RX
chance% nuttcp -w2m 192.168.88.8
3613.9449 MB / 10.02 sec = 3025.0659 Mbps 42 %TX 44 %RX
chance% nuttcp -r -w2m 192.168.88.8
2720.0625 MB / 10.02 sec = 2276.8601 Mbps 30 %TX 33 %RX
chance% nuttcp -w2m 192.168.88.8
3212.8971 MB / 10.02 sec = 2689.3386 Mbps 37 %TX 42 %RX
chance% nuttcp -r -w2m 192.168.88.8
3357.0360 MB / 10.02 sec = 2810.3478 Mbps 39 %TX 42 %RX
chance% nuttcp -w2m 192.168.88.8
3211.4634 MB / 10.02 sec = 2687.7779 Mbps 36 %TX 39 %RX
chance% nuttcp -r -w2m 192.168.88.8
2721.7613 MB / 10.02 sec = 2278.5156 Mbps 30 %TX 37 %RX
chance% nuttcp -w2m 192.168.88.8
3644.1250 MB / 10.02 sec = 3051.0836 Mbps 44 %TX 41 %RX
chance% nuttcp -r -w2m 192.168.88.8
3645.9113 MB / 10.02 sec = 3052.3410 Mbps 42 %TX 45 %RX
chance% nuttcp -w2m 192.168.88.8
3647.8125 MB / 10.02 sec = 3054.8793 Mbps 42 %TX 43 %RX
chance% nuttcp -r -w2m 192.168.88.8
2632.4584 MB / 10.03 sec = 2202.3219 Mbps 30 %TX 34 %RX
chance% nuttcp -w2m 192.168.88.8
3116.7845 MB / 10.02 sec = 2608.9506 Mbps 35 %TX 37 %RX
chance% nuttcp -r -w2m 192.168.88.8
3656.5440 MB / 10.02 sec = 3062.0011 Mbps 43 %TX 43 %RX
chance% nuttcp -w2m 192.168.88.8
2595.8413 MB / 10.02 sec = 2172.9548 Mbps 28 %TX 30 %RX
chance% nuttcp -r -w2m 192.168.88.8
3647.7545 MB / 10.02 sec = 3054.6487 Mbps 42 %TX 44 %RX
[TCP performance is consistently poor - ranging between 2 to 3 Gbps
which is a performance hit of 40% to 60% relative to the excellent
network performance with 2.6.12.6]
[average TCP performance is 2812 Mbps (47.6% performance drop from 2.6.12.6]
--------------------------------------------------------------------------------
2.6.14.3 multiple stream network performance test:
--------------------------------------------------------------------------------
[2 streams]
chance% nuttcp -Is1 -w2m 192.168.88.8 & nuttcp -Is2 -w2m -p5002 192.168.88.8
s1: 2377.2733 MB / 10.02 sec = 1989.6904 Mbps 14 %TX 36 %RX
s2: 1763.1018 MB / 10.04 sec = 1473.8191 Mbps 10 %TX 23 %RX
[aggregate TCP throughput of 3463.5095 Mbps]
chance% nuttcp -Is1 -w2m 192.168.88.8 & nuttcp -Is2 -w2m -p5002 192.168.88.8
s1: 2428.4656 MB / 10.03 sec = 2030.1821 Mbps 26 %TX 39 %RX
s2: 1372.3125 MB / 10.04 sec = 1146.0622 Mbps 11 %TX 16 %RX
[aggregate TCP throughput of 3176.2443 Mbps]
chance% nuttcp -Is1 -w2m 192.168.88.8 & nuttcp -Is2 -w2m -p5002 192.168.88.8
s1: 3604.3959 MB / 10.02 sec = 3017.7727 Mbps 63 %TX 46 %RX
s2: 1801.3750 MB / 10.02 sec = 1507.3981 Mbps 13 %TX 28 %RX
[aggregate TCP throughput of 4525.1708 Mbps]
chance% nuttcp -Is1 -w2m 192.168.88.8 & nuttcp -Is2 -w2m -p5002 192.168.88.8
s1: 2996.8977 MB / 10.02 sec = 2508.4744 Mbps 32 %TX 35 %RX
s2: 1795.0000 MB / 10.02 sec = 1502.0434 Mbps 26 %TX 24 %RX
[aggregate TCP throughput of 4010.5178 Mbps]
chance% nuttcp -Is1 -w2m 192.168.88.8 & nuttcp -Is2 -w2m -p5002 192.168.88.8
s1: 3531.6250 MB / 10.02 sec = 2957.1683 Mbps 70 %TX 49 %RX
s2: 1766.9590 MB / 10.03 sec = 1477.8697 Mbps 12 %TX 27 %RX
[aggregate TCP throughput of 4435.0380 Mbps]
[3 streams]
chance% nuttcp -Is1 -w2m 192.168.88.8 & nuttcp -Is2 -w2m -p5002 192.168.88.8 &
nuttcp -Is3 -w2m -p5003 192.168.88.8
s1: 3183.1493 MB / 10.02 sec = 2665.1879 Mbps 67 %TX 44 %RX
s2: 1583.1875 MB / 10.04 sec = 1322.9457 Mbps 27 %TX 26 %RX
s3: 1581.6250 MB / 10.04 sec = 1321.7448 Mbps 29 %TX 26 %RX
[aggregate TCP throughput of 5309.8784 Mbps]
chance% nuttcp -Is1 -w2m 192.168.88.8 & nuttcp -Is2 -w2m -p5002 192.168.88.8 &
nuttcp -Is3 -w2m -p5003 192.168.88.8
s1: 2719.9508 MB / 10.02 sec = 2277.1130 Mbps 57 %TX 34 %RX
s2: 2577.6250 MB / 10.04 sec = 2154.1221 Mbps 50 %TX 46 %RX
s3: 1095.7412 MB / 10.05 sec = 914.5157 Mbps 21 %TX 16 %RX
[aggregate TCP throughput of 5345.7508 Mbps]
chance% nuttcp -Is1 -w2m 192.168.88.8 & nuttcp -Is2 -w2m -p5002 192.168.88.8 &
nuttcp -Is3 -w2m -p5003 192.168.88.8
s1: 1128.8511 MB / 10.04 sec = 943.0773 Mbps 22 %TX 19 %RX
s2: 2996.2500 MB / 10.03 sec = 2505.4041 Mbps 93 %TX 42 %RX
s3: 1987.1875 MB / 10.03 sec = 1661.9869 Mbps 35 %TX 32 %RX
[aggregate TCP throughput of 5110.4683 Mbps]
chance% nuttcp -Is1 -w2m 192.168.88.8 & nuttcp -Is2 -w2m -p5002 192.168.88.8 &
nuttcp -Is3 -w2m -p5003 192.168.88.8
s1: 2760.1107 MB / 10.02 sec = 2310.9835 Mbps 52 %TX 41 %RX
s2: 1374.7603 MB / 10.03 sec = 1150.1740 Mbps 27 %TX 21 %RX
s3: 2279.8210 MB / 10.03 sec = 1906.1184 Mbps 46 %TX 33 %RX
[aggregate TCP throughput of 5367.2759 Mbps]
chance% nuttcp -Is1 -w2m 192.168.88.8 & nuttcp -Is2 -w2m -p5002 192.168.88.8 &
nuttcp -Is3 -w2m -p5003 192.168.88.8
s1: 1722.2500 MB / 10.03 sec = 1440.9805 Mbps 27 %TX 28 %RX
s2: 1274.6456 MB / 10.04 sec = 1064.5976 Mbps 22 %TX 17 %RX
s3: 2515.2596 MB / 10.03 sec = 2104.1241 Mbps 46 %TX 34 %RX
[aggregate TCP throughput of 4609.7022 Mbps]
--------------------------------------------------------------------------------
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
