Based on previous findings on CPU counting in public clouds, we look at an example where it makes a big difference: software licensing, particularly Oracle. Additional licensing costs resulting from CPU counting can dwarf any cost savings on infrastructure. We talk about how this happens, and show an example.
After looking at how virtual CPUs are handled in Amazon Web Services and Microsoft Azure, we explore CPU definitions and CPU performance under the Google Compute Engine platform.
I’ve been doing some testing to clarify what a vCPU in Amazon Web Services actually is. Over the course of the testing, I experienced inconsistent results on a 2-thread test on a 4-vCPU m3.xlarge system, due to the mislabeling of the vCPUs as independent single-core processors by the Linux kernel. This issue manifests itself in…
The definition of a vCPU in Amazon Web Services is a bit unclear. We run some tests to see how much CPU performance we actually get, and discover some unexpected side effects from AWS’s implementation.
It’s yet again time for Oracle’s critical patch update (CPUJAN2008). The update will be released on Tuesday January 15, and as of yet there are no details on exactly what vulnerabilities have been found.