I have had a couple of Power systems administrators make assumptions about the virtual Ethernet speed improvements when they install a 10 Gb IVE/HEA in a VIOS which are simply not true. I guess that if three teams have made this mistake then others are about too. So I intend here to put the record straight.
The expectation is that (deliberately fully spelt out long-hand to make it very clear):
- When they upgrade the Integrated Virtual Ethernet (also called a Host Ethernet Adapter) from 1 Gigabit per second to 10 Gigabit per second
- that the Virtual Ethernet inside the machine which runs at about 1 Gigabit per second beforehand will also jump to 10 Gigabit per second
- so that the Virtual machines (LPAR) using the Virtual I/O Server (VIOS) Shared Ethernet Adapter (SEA) will benefit from the increase network speed.
- That is the client virtual machines speed jump from 1 Gb/s to 10 Gb/s to the external network.
Sorry guys but this is not true!
Below are my comments:
- It is fundamentally true that the performance between two nodes across a network is constrained by the weakest link.
- The virtual Ethernet speed is not related to the physical adapter speed of the adapter in the VIOS - I am not sure why that is assumed.
- Perhaps the speed of the 1Gb /s Ethernet adapter or 1 Gb/s IVE/HEA being similar to the typical speeds of the virtual Ethernet which are 0.5 Gb/s to 1.5 Gb/s lead many people to believe or assume the physical adapter or IVE/HEA was a limiting factor but it is not.
- If it was true then virtual machine to virtual machine speed (i.e. without that limit) would be much faster but it is not.
- The virtual Ethernet function is performed by the Power5 or Power6 or Power7 main processors providing the TCPIP multiple layers of packet handling and then communication via hypervisor data structures plus interrupts across the machine via the Hypervisor. The actual blocks of data in memory are not moved (a very expensive CPU operation) as the Hypervisor can perform this function via virtual memory address space remapping the translations of the memory blocks (which takes some CPU cycles but much less). But all these CPU control and virtual memory operations do take elapsed time and CPU cycles.
- Note: the simplest way to reduce virtual Ethernet performance is to not have enough Power CPU cycles available to your source and target virtual machines (LPARs). For example by capping your virtual with too low and Entitlement, too low a virtual CPU number, low Entitlements and forcing the virtual machine to compete for extra CPU time from the pool or too small a CPU pool.
- The physical PCIe adapter or IVE/HEA has a dedicated processor on-board to provide these function off-loaded from the main CPUs and get the data via DMA (Direct Memory Access) with no Power CPU cycles. When you upgrade the adapter I think it is safe to assume you upgrade the Ethernet media speed and probably the adapter processor to handle the increased bandwidth.
Referring to the below diagram:
- The network speed between virtual machine A and virtual machine B is purely due to the virtual Ethernet speed - something like 0.5 to 1.5 Gb/s.
- The network speed between virtual machine A and the VIOS is the
virtual Ethernet speed - as above.
- The network speed between virtual machine A and target outside of the machine via the VIOS SEA is the lower of the
virtual Ethernet speed and the physical network speed.
Of course, the VIOS using a 10 Gb/s physical adapter or IVE/HEA can maintain much higher external network speed for ALL the virtual machines as each virtual machine can con-currently be sending and receiving network data at the virtual Ethernet speed.
- If the external network is 1 Gb/s then this it is the limiting factor.
- If the external network is 10 Gb/s then the virtual Ethernet is the limiting factor i.e. about 1Gb/s.
Virtual machine C is not using the virtual Ethernet. If it has a 10 Gb/s adapter or IVE/HEA then is can reach higher speeds to other nodes on the network like for example, 5 to 7 Gb/s. The speed depends on a number of things including
Converting virtual machines A or B at around 1 Gb/s to a type C virtual machine will get you a jump of 5 to 7 times network speed.The Shared Ethernet Adapter (SEA) on the VIOS does require Power CPU cycles (so don't starve you VIOS of compute time) but does not limit network speeds. The bridging is done at a lower TCPIP stack level for maximum efficiency.
- Power CPU cycles available in the virtual machine as running higher speed networks does take considerably more Power CPU cycles for device drivers and interrupts. This is often over looked and is true for virtual or physical networks.
- Dealing with the data itself - reading the data from disk or creating it or dealing with incoming data or just saving it to disk.
- External network contention - although modern Ethernet switches avoid a lot of packet collisions and resends.
- The far end also has to deal with the data - we often hit this limitation when tuning our end of a network without realising it. I often get ask - what is stopping AIX going faster and its not our end that is the issue.
- Tuning of the local operating system in flow control, RFA settings, buffering etc. see the "no" commands for lots of options.
- Large packet always helps as you then get more bytes per network "transaction" - each transaction costs CPU cycles and interrupts.
The bottom line is the virtual Ethernet speed is not effected by VIOS physical adapter - either PCIe or IVE/HEA.
Well I hope this clears up this erroneous assumption and you have better expectations of the effects of a VIOS network adapter upgrade, thanks, Nigel Griffiths.