NimbostratusIn the BIG-IP® Virtual Edition and VMware ESXi setup guide for version 12.1, the document specifies that in "VMware ESXi 5.5 and later, do not set the number of virtual sockets to more than 2."
What I am wondering is if anyone knows the consequences of running more than two virtual sockets on a BIG-IP VE appliance?
NimbostratusMore info:
We recently converted from some ageing physical appliances and since we went live we have seen an increase in response times from a web service that has a sub-second SLA. Mostly ping times to the web service from outside the LTM are around a millisecond, put periodically they'll climb to as much as 200-300 milliseconds. My first instinct was that we might have a CPU scheduling issue at the VMWare layer, so I set CPU reservations but that didn't impact the problem. During further investigation I ran across the discrepancy in the number of sockets. I plan on changing the config to 2 dual core virtual sockets during our next maintenance window, but I'm still curious if anyone has any idea about what performance would be like in current conditions.
CumulonimbusHi,
One of reason is the throughput limit per core
https://support.f5.com/csp/article/K14356
Another one is there are vCPU limitations depending of purchased license
https://support.f5.com/csp/article/K14810