Thought frequently mentioned, Phoronix did not run a benchmark comparing before and after application of the microcode update. Excerpt: To note, no microcode changes/updates were made to the systems under test for this article, just testing/comparing the kernel patches (https://www.phoronix.com/scan.php?page=article&item=l1tf-for...)
> For companies like Google and Microsoft with the ability to get custom chips, and with custom schedulers that can ensure that VMs to not cross hyper-threading boundaries, this is something that can be relatively easily mitigated. For enterprise virtualization clouds, this may increase utilization of underutilized servers, and cause more server purchases in the future.
Is this net-positive for VMware since customers will be required to buy more licenses for the same workload?
Or is it net-negative because it makes public clouds more competitive?
Is this net-positive for VMware since customers will be required to buy more licenses for the same workload?
Or is it net-negative because it makes public clouds more competitive?