I always have two vmnic3 interfaces to each of my CHRs.

I do not use any CHRs for do-everything routers, To have VmWare ESXi reboot with delayed_ack enabled - you need to vi ( edit a file )Īnd place this line inside the local.sh fileĪdd this or change the file to contain the line below The above two commands take place right away - no vmware esxi reboot needed. Vsish -e set /net/tcpip/instances/defaultTcpipStack/sysctl/_net_inet_tcp_delayed_ack 0

Vsish -e set /net/tcpip/instances/defaultTcpipStack/sysctl/_net_inet_tcp_delayed_ack 1 In the VmWare ESXi shell, here are some delayed_ack commands: This is from my notes I have compiled over the years: Question, what is the license level you have on your CHR ?Īlso - try changing your MTU to 1500 for everything ( VmWare ESXi server ) and your network switches and any MTU settings in vm machines. Question, is the total CPU count for all virtual machines less than the total cores you physically have ?

Sometimes, this can get you a 500+ percent increase in network I/O throughput. ( Don't ping-pong your traffic between VmWare ESXi servers.Īlso - If you are strong on networking, take a look at Delayed-Ack in your network settings in your physical and virtual servers. group your virtual servers together as much as possible to avoid traffic from one VmWare ESXi server going to another Physical VmWare ESXi server, then going back. If you have multiple physical VmWare ESXi servers Use physical 10-Gig ( or 100-Gig ) network cards instead of 1-GIg network cards. Use paravirtual interfaces where possible Use Vmnic3 network interfaces where possible. Limit the total number of CPUs assigned to virtual servers to have a combined CPU usage of one less than the actual of physical CPU cores you have. In the BIOS on your physical VmWare ESXi server, disable hyper-threading. If you have a VmWare ESXi server that is showing high CPU usage - try this :

Chr router