Benchmark an Application


The Benchmark feature lets you deploy an application profile across multiple cloud providers or cloud regions from a single cloud provider and produces a report that helps you optimize cost and performance.

On the cloud, price and performance are inextricably linked. Knowing one without the other is of little use given inherent trade offs and changing cloud landscape. 

Benchmark Process

Workload Manager automates the benchmark tasks for the price, performance, and price-performance index for each application, across any cloud, instance type or provider, so you can pick your target before you migrate.

Benchmark costs are calculated based on the Job cost and Node cost and are updated hourly. Once the benchmark completes, it is essential to wait for at least 1 hour before checking the benchmark results.

The Schedule Benchmark task allows you to run a benchmark for an application at a scheduled time. See Application Profiles PageSchedule Benchmarks for additional context.

 Cloud Nuances -- VMware and OpenStack

When running benchmarks for legacy applications on VMware or OpenStack clouds, you must wait until the data is loaded. If you enter any information before the data is loaded then the Submit button is disabled.

Load Generator

The last page of the Benchmark form is similar to Page 2 of the Deploy form, where you can set the instance type, volumes, and cloud settings for each tier of your application. However, there is one important difference: before the per tier settings for each of the tier of your application is an extra unlabeled tier. This is the load generator tier.  Select the instance type, volumes and cloud settings for this tier as you would for other application tiers. 

The Load Generator tier is based on the CentOS 6.x logical image. Therefore, for the benchmark deployment to succeed, a CentOS 6.x physical image must exist in each region where the benchmark will be run and the CentOS 6.x logical image must be mapped to the corresponding CentOS 6.x physical image in each of these cloud regions. Furthermore, each mapping must include at least one instance type. See Images Page for more context.

  • No labels
Terms & Conditions Privacy Statement Cookies Trademarks