
6
VMWARE WHITE PAPER
To ensure that the secondary virtual machine runs as fast as the primary, it is recommended that:
• ThehostsintheFTclusterarehomogenous,withsimilarCPUmake,model,andfrequency.TheCPUfrequencydifferenceshould
not exceed 400 MHz.
• Boththeprimaryandsecondaryhostsusethesamepowermanagementpolicy.
• CPUreservationissettofullforcaseswherethesecondaryhostcouldbeoverloaded.TheCPUreservationsettingontheprimary
applies to the secondary as well, so setting full CPU reservation ensures that the secondary gets CPU cycles even when there is
CPU contention.
2.4. I/O Latencies
All incoming network packets to the primary, and all disk reads at the primary, are immediately sent to the secondary. However, as
explained in section 1.4, network transmits and disk writes at the primary are held until the secondary acknowledges that all events
that precede the packet transmit or disk write. As a result, the round-trip network latency between the primary and the secondary
aectstheI/Olatencyofdiskwritesandnetworktransmitoperations.SincetheroundtriplatencyinaLANenvironmentisusuallyin
the order of a few hundred microseconds, and disk I/O latencies are usually on the order of a few milliseconds, this delay does
not impact disk write operations. One may, however, notice delays in network ping responses if the response time is shown in
microseconds. For best performance, it is recommended that the round-trip network latency between the primary and secondary
host be less than 1 millisecond.
2.5. Network Link
Since the primary and secondary virtual machines proceed in vLockstep, the network link between the primary and the
secondary host plays an important role in performance. A Gigabit link is required to avoid congestion. In addition, higher bandwidth
network interfaces generally have lower transmission latency. If the network is congested and the primary host is not able to send
trac to the secondary (i.e. when the TCP window is full), then the primary virtual machine will make little or no forward progress. If
the network connection between the primary and secondary hosts goes down, either the current primary or the current secondary
virtual machine will take over, and the other virtual machine will die.
2.6. NIC Assignments for Logging Traffic
FT generates two types of network trac:
• Migrationtraffictocreatethesecondaryvirtualmachine
• FTloggingtraffic
MigrationtrachappensovertheNICdesignatedforVMotionanditcausesnetworkbandwidthusagetospikeforashorttime.
SeparateanddedicatedNICsarerecommendedforFTloggingtracandVMotiontrac,especiallywhenmultipleFTvirtual
machinesresideonthesamehost.SharingthesameNICforbothFTloggingandVMotioncanaecttheperformanceofFTvirtual
machines whenever a secondary is created for another FT pair or a VMotion operation is performed for any other reason.
VMwarevSwitchnetworkingallowsyoutosendVMotionandFTtractoseparateNICswhilealsousingthemasredundantlinksfor
NICfailover.SeeKB article 1011966 for more information.
Adding multiple uplinks to the virtual switch does not automatically result in distribution of FT logging trac. If there are multiple FT
pairs, then trac could be distributed with IP-hash based load balancing policy, and by spreading the secondary virtual machines to
dierent hosts.
2.7. Virtual Machine Placement
FT logging trac is asymmetric: the bulk of the trac ow happens from the primary to the secondary hosts and the secondary host
only sends back acknowledgements. If multiple primary virtual machines are co-located on the same host, they could all compete for
thesamenetworkbandwidthontheloggingNIC.Idlevirtualmachinesconsumelessbandwidth,butI/O-intensivevirtualmachines
can consume a lot of network bandwidth. It can be helpful to place the primary of one FT pair and the secondary of another FT pair
onthesamehosttobalancethetracontheFTloggingNIC.