How does CloudSigma's CPU performance compare with other clouds?


The first thing to say is that CPU performance is a very multi-faceted beast. There’s no one magic measure or benchmark, for that reason you can make pretty much any cloud look like ‘the best’ in the right light. It’s why we don’t publish our own benchmarks in-house, they just don’t have credibility for a discerning audience.

CPU performance holistically comes from the interplay of a number of factors which you can think of as layers. The first is the raw underlying potential of the actual hardware, clearly an older slower processor has a lower maximum potential than a newer, faster one. The second layer is the hypervisor translation layer and how efficient that is and whether resources are being over-allocated/contended. Finally you have the fit/efficiency between how the CPU is exposed and what your application ideally wants to see. The final one is things like ideal number of CPU threads, CPU instruction sets, NUMA topology and other such details that can make a huge difference to computing in the real world.

I’m outlining below how we deliver high performance computing to customers in light of the above factors.

Factor 1: Raw underlying hardware potential
We have a fast two year replacement cycle on all hardware. It means the average life of a compute node in CloudSigma is less than one year old (because we are growing so we add more new nodes than the old ones we replace). This ensures you are on modern processors not just initially, but always.

Factor 2: Hypervisor Efficiency & Resource Contention
We use the Linux KVM hypervisor. Not only is KVM widely recognized as one of the most, if not the most, secure hypervisor out there, it’s also a very efficient one offering full resource isolation for each customer. As a result, the translation layer between raw underlying potential and the maximum throughput that can be achieved through the hypervisor is much smaller than it might otherwise be. Customers report typically a 5-10% virtualisation overhead with KVM and it’s shrinking as KVM gains more and more momentum.

Our proprietary cloud stack monitors load on each individual compute node to prevent contention of customer computing, in this way you’ll always get the CPU throughput you’ve paid for unlike other platforms that slow down during busy times.

Factor 3: CPU Settings & Customization
Unlike most other platforms, should you wish you can make a large number of customizations to how CPU and memory are exposed to the cloud servers you have and you can do this on a cloud server by cloud server basis. Whether it’s exposing the native CPU instruction set, having visibility over NUMA topology or optimising the number of CPU threads, it’s all possible on our platform. The result for a customized platform is the best price/performance in the business.

Take a look at this comprehensive comparison of cloud server performance across various providers on the market.

Marked as spam
Asked on July 12, 2018 1:23 pm