Eric Sloof

You can use "Applied to" to apply the rules within policy to a selected group. By default, the policy Applied to field is set to DFW, and the policy rules are applied to all workloads.

Applied to defines the scope of enforcement per policy, and is used mainly for optimization of resources on ESXi and KVM hosts. It helps in defining a targeted policy for specific zones, tenants or applications, without interfering with other policy defined for other applications, tenants and zones.

In this example I have three security groups: App, DB and Web. When I apply the "Allow DB Traffic" rule to the DFW, all rules including the highlighted App to DB rule are tied to the Web VM.

When I use a security group instead of DFW, I can narrow down the rules that are tied to the network adapter of  the Web VM.

In the next screenshot we can see that the highlighted rule has disappeared from the list.

VMware vSphere 7.0 U2 includes a CPU scheduler that is architecturally optimized for AMD EPYC. This scheduler is designed to take advantage of the multiple last-level caches (LLCs) per CPU socket offered by the AMD EPYC processors.

This paper shows that vSphere 7.0 U2 can achieve near optimal performance with this new CPU scheduler using out-of-the-box BIOS options and vSphere settings.

An extensive performance evaluation using both enterprise benchmarks and microbenchmarks shows that the CPU scheduler in vSphere 7.0 U2 achieves up to 50% better performance than 7.0 U1.