Server applications must exchange data with end users and storage subsystems, so effective server virtualization...
By submitting your personal information, you agree that TechTarget and its partners may contact you regarding relevant content, products and special offers.
must also include solid network performance. Inefficient configurations and latency can conspire against workloads and impair the user experience. Fortunately, hypervisors like VMware ESXi provide ample tools to measure network latency along with techniques for increasing efficiency.
Free point tools like Iperf or Iometer are often recommended for ad-hoc network performance testing. The goal is to test the maximum bandwidth from strategic points in the environment. For example, test bandwidth at the suspect virtual machine, test bandwidth on a system outside of the virtualized host server, test bandwidth on a system outside of the virtualized host on the same VLAN, and then test bandwidth on two VMs on the same virtualized server and vSwitch.
After you measure network latency, compare results and look for the presence of possible network bottlenecks. For example, poor network performance on only one VM may suggest resource allocation problems -- CPU and memory -- to that troubled workload. By comparison, network issues afflicting every workload on a specific server -- while other servers perform normally -- may suggest possible network configuration issues or trouble with the server's network interface cards or software optimization issues like improper traffic shaping or incompatible jumbo frame configurations. And network performance issues with related server groups may suggest network problems such as a fault in a common shared switch. There are certainly other possible causes to consider, but using tools to evaluate the problem's scope is a standard troubleshooting tactic that can help narrow the cause.
If you do choose to use tools like Iperf to measure network latency, VMware suggests changing the TCP window size to 64 KB at the client and server sides. Smaller TCP sizes may cause excess handshakes resulting in unexpectedly low network performance results. Refer to the instructions for your specific tool in order to define the optimum TCP window size or other test settings that are most appropriate for your particular environment.
How VMware NSX will change networking jobs
Five key networking features in vSphere 5
Applying virtual networking concepts to your data center
Dig Deeper on Virtual machine monitoring, troubleshooting and alerting
Related Q&A from Stephen J. Bigelow
RAID 5 and RAID 6 are two types of erasure coding. The former protects data with basic parity, while the latter builds in a second layer of parity ...continue reading
Cleanly divided and straightforward applications are good candidates for a container-based deployment, whereas complex applications pose more ...continue reading
Assessing the impact of containers on application workloads can be extremely challenging, partially because of how quickly containers are spun up and...continue reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.