Cloud Vendor Report: NxtGen ECS

The Study

NxtGen commissioned a benchmarking analysis report to examine the relative performance of major VM components including virtual cores, memory, block storage, and internal network for NxtGen Enterprise Cloud Services (ECS), Amazon Web Services (AWS), and Rackspace Cloud Servers. Specifically, the study examines raw performance and price-indexed performance for two common workloads: web servers and databases. Findings from the study show that NxtGen ECS provides competitive levels of raw performance and price-indexed performance. NxtGen displayed particularly strong price-performance value, providing the most value across all five use cases examined in the study.

• For the majority of tests, NxtGen exhibited the highest storage and internal network performance; Rackspace exhibited the highest vCPU and memory performance.
• NxtGen exhibited the highest price-performance value across all tests and workload scenarios.

For this study, Cloud Spectator evaluated performance by benchmarking the VMs using Geekbench 3, FIO and Iperf. The respective benchmarks measured vCPU & Memory, Storage and Internal Network. Testing occurred over the course of a 5-day period. Pricing was examined in conjunction with the performance tests.

The Method

Cloud Spectator tested virtual machines from Amazon, NxtGen, and Rackspace for a period of five days between March 17, 2015 and March 21, 2015. One-iteration of the test suite was run per day. Each iteration captured performance data on virtual processors, memory bandwidth, block storage IOPS, and internal network throughput. Block storage was tested instead of local, ephemeral storage because of its persistence, resiliency and dependability. Tests within the suite are categorized in the table below.

Table 1: The tests listed in this table were used to collect quantitative data on performance across the selected VMs (see Table 2) on all the providers examined in the study.

 
In an effort to standardize VM sizes between the providers, comparable virtual machine sizes were chosen based on equivalent amounts of virtual cores reported by the provider. Block storage was matched by comparing a 100GB, 500GB or 1000GB volume attached to each VM. A separate, equivalently sized virtual machine was provisioned within the same region/availability zone to act as a server for internal network testing. All virtual machines ran using Ubuntu Linux 14.04. The c4 instance type was selected for the Amazon 2vCPU VM comparison despite offering more memory than the comparable VMs on the other providers. At the time of the study, the c4 instances were the closest match to the other two providers’ VM sizes. The amount of memory of the c4 instances did not significantly affect the memory bandwidth performance. Amazon and Rackspace machines were provisioned in data centers as close to NxtGen’s Bangalore data center as possible. Table 2 provides details of VMs used for each provider.

Table 2: illustrates the VMs that were used in the comparison standardized by vCPU cores.
*Note: Amazon Block Storage testing examined EBS General Purpose (SSD) volumes; Rackspace Block Storage testing examined the Cloud Block Storage SSD volumes; NxtGen Block Storage testing examined the SSD Storage volumes

 
The CloudSpecs Score, which is an indexed score for price-performance value, was calculated by taking the monthly price of each server size and performance results of the components and using a formula to find the level of performance per unit of price. The resulting number was then pegged to the highest result for that server class, which gets a score of 100; thus, value numbers are relative.

For example, if Provider A scores 100 and Provider B scores 50, then Provider A shows 2x more price-performance value than Provider B. Please see the formula below to calculate the CloudSpecs Score.

1. provider_value = {provider performance score} / {provider cost}
2. best_provider_value = max{provider_values}
3. Provider’s CloudSpecs Score = 100*provider_value / best_provider_value

Table 3: The table above shows the price of the VMs used on the three providers. Rackspace pricing incorporates the required service fee at the Managed Infrastructure level. For providers with hourly pricing, usage of 730 hours per month was assumed in the monthly pricing above.

 
A CloudSpecs score was produced for each of the following components on all the providers: vCPU, memory, sequential/random read/write IOPS, and internal network (see Table 4). The separate scores were aggregated based on the relevant components examined in each category to produce a VM CloudSpecs Score for each virtual machine size. The VM CloudSpecs scores were then averaged to produce the Category’s CloudSpecs Score. For example, on the Static Web Server:

1. VM CloudSpecs Score = ({vcpu_cloudspecs_score} + {read_iops_cloudspecs_score})/2
2. Static Web Server CloudSpecs Score = ({2vcpu_VM_CloudSpecs_Score} + {4vcpu_VM_CloudSpecs_Score})/2

The Use-Cases

Web Servers
NxtGen’s web server performance was examined in three categories: (1) static web server, which includes small websites; (2) read/write web server, which covers a majority of websites that users can download and upload content from/to; and (3) high-traffic web server, which encompasses large web architectures that sustain high amounts of traffic and transactions.

Databases

 
Apart from the different database applications available, such as MySQL, PostgreSQL, Microsoft SQL, and Oracle, the applicable virtual machine sizes for database environments and numerous use cases can make benchmarking a particular database a very complex process. Cloud Spectator’s approach in this study examines the server-side factors involved that affect database performance, namely the processor, memory, disk, and—in the case of large, distributed databases—internal network.

May 2015 Web Host Performance Update
June 15, 2015

Cloud Vendor Evaluation: 1&1
June 1, 2015

April 2015 Web Host Performance Update
May 6, 2015

Amazon EC2 Instance Comparison: C3 vs. C4
April 21, 2015

March 2015 Web Host Performance Update
April 13, 2015

February 2015 Web Host Performance Update
March 10, 2015