Intel 7xx Servers, 170 Servers manual TCP/IP non-secure performance, Streaming Performance

Virtual Ethernet		Performance in MB per second
FTP		1 Disk Unit ASP on 2757 IOA	15 Disk Units ASP on 2757 IOA
1	Session	10.8	42.0
2	Sessions	10.5	70.0
3	Sessions	10.4	75.0

5.4 TCP/IP non-secure performance

In table 5.4 you will find the payload information for the different Ethernet types. The most important factor with streaming is to determine how much data can be transferred. The results are listed in bits and bytes per second. Virtual Ethernet does not have a raw bit rate, since the maximum throughput is determined by the CPU.

Table 5.4

Streaming Performance

Ethernet Type		Raw bit rate1	MTU2	Payload Simplex3	Payload Duplex4
		(Mbits per second)		(Mbits per second)	(Mbits per second)
	100 Megabit	100	1,492	93.5	170.0
	1 Gigabit	1,000	1,492	935.4	1740.3
			8,992	935.9	1753.1
	10 Gigabit5	10,000	1,492	3745.4	4400.7
			8,992	8789.6	9297.0
		1,000	1,492	986.4	1481.4
HEA 1 Gigabit			8,992	941.1	1960.9
		160,007	1,492	2811.8	6331.0
			8,992	9800.7	10586.4
		10,000	1,492	2913.1	3305.2
HEA 10 Gigabit			8,992	9392.3	9276.9
		160,007	1,492	2823.5	6332.3
			8,992	9813.7	10602.3
	Blade8	n/a	1,492	933.1	1014.4
	Virtual6	n/a	8,992	8553.0	11972.3
Notes:
1.	The Raw bit rate value is the physical media bit rate and does not reflect physical media overheads
2.	Maximum Transmission Unit. The large (8992 bytes) MTU is also referred to as Jumbo Frames.
3.	Simplex is a single direction TCP data stream.
4.	Duplex is a bidirectional TCP data stream.
5.	The 10 Gigabit results were obtained by using multiple sessions, because a single sessions is incapable to fully utilize the
	10 Gigabit adapter.
6.	Virtual Ethernet uses Jumbo Frames only, since large packets are supported throughout the whole connection path.
7.	HEA P.P.U.T (Partition to Partition Unicast Traffic or internal switch) 16 Gbps per port group.
8.	4 Processor 7998-61X Blade
9.	All measurements are performed with Full Duplex Ethernet.

Streaming data is not the only type of communication handled through Ethernet. Often server and client applications communicate with small packets of data back and forth (RR). In the case of web browsers, the most common type is to connect, request and receive data, then disconnect (ACRR). Table 5.5 provides some rough capacity planning information for these RR and ACRR communications.

Table 5.5

IBM i 6.1 Performance Capabilities Reference - January/April/October 2008
© Copyright IBM Corp. 2008	Chapter 5 - Communications Performance	68