VMmark is a free tool used by hardware vendors and others to measure the performance, scalability, and power consumption of virtualization platforms.
The VMmark benchmark:
A cloud environment typically collects several diverse workloads onto a virtualization platform — a collection of physical servers accessing shared storage and network resources. Traditional single-workload performance and scalability benchmarks for non-virtualized environments were developed with neither virtual machines nor cloud environments in mind. Even single-server virtualization benchmarks did not fully capture the complexities of today's virtualized data centers.
VMmark 1.x pioneered single-server virtualization benchmarking with its unique tile-based multi-application design. VMmark 2.x expanded this to multiple servers and platform-level workloads. Applications have evolved since then, and VMmark 3 addresses these changes in application architecture and platform-level operations. More than ever before, users are running highly scalable workloads, often referred to as third platform applications, and increasingly complex OLTP workloads.
VMmark 3 features a highly automated setup and tile-cloning process that makes benchmark deployment fast and easy, with the need for very little manual intervention. VMmark 3 uses free or open-source software throughout, eliminating the need to purchase software licenses, and the VMmark .ova includes all the needed software in one downloadable template.
The VMmark benchmark combines commonly-virtualized applications into predefined bundles called "tiles." The number of VMmark tiles a virtualization platform can run, as well as the cumulative performance of those tiles and of a variety of platform-level workloads, determine the VMmark 3 score.
Before being published, VMmark results must be submitted to a review panel composed of a variety of companies that have published VMmark benchmark results, ensuring the fairness and integrity of the benchmark.
Since its inception in 2007, more than 200 VMmark results have been published on the VMmark website and VMmark has become the standard by which the performance of virtualization platforms is evaluated.
VMmark uses workloads representative of the highly scalable and complex applications commonly found in the data center. VMware has worked closely with its partners to design and implement the benchmark and has gathered extensive customer feedback to understand how these applications are typically used in virtualized environments.
Elasticity is critical in measuring the real-world workloads that are found in today’s datacenters. The act of adding and subtracting resources to meet demands is now more common than ever for self-scaling applications. VMmark 3 adds this component alongside a cyclical application profile to more accurately represent today’s bursty environments.
The unit of work for a virtualized data center can be usefully defined as a collection of virtual machines executing a set of diverse workloads. The VMmark benchmark refers to this unit of work as a "tile." Each VMmark tile is paired with a client system that drives the tile’s virtual machines to perform a variety of tasks, some internal to each virtual machine, some involving other virtual machines in the tile, and some involving the client system.
The total number of tiles that multiple systems in the data center can accommodate, while infrastructure operations are performed in the background, provides a coarse measure of that data center's consolidation capacity. The performance of the workloads within those tiles provides a fine measure of the data center's overall performance and, combined with the performance of the administrative operations, is used to calculate a VMmark benchmark score.
The rapid pace of innovation has quickly transformed typical server usage by enabling easier virtualization of bursty and heavy workloads, dynamic virtual machine relocation (vMotion), dynamic datastore relocation (storage vMotion), and automation of many provisioning and administrative tasks across large-scale multi-host environments. In this paradigm, a significant proportion of the stresses on the CPU, network, disk and memory subsystems can be generated by the underlying infrastructure operations. Load balancing across multiple hosts can also greatly affect application performance. Any relevant benchmarking methodology must still focus on user-centric application performance while accounting for the effects of this infrastructure activity on overall platform performance. VMmark 3 generates a realistic measure of platform performance by incorporating a variety of platform-level workloads such as shared nothing migration, virtual machine migration, clone and deploy, snapshotting, and storage migration operations, in addition to traditional application-level workloads.
During a VMmark benchmark run, which lasts at least three hours, individual performance metrics are collected every 60 seconds. Each of these metrics represents the performance of an individual application or infrastructure workload.
The application workload metrics for each tile are computed and aggregated into a score for that tile by normalizing the different performance metrics, such as operations/second or transactions/second, with respect to a reference system. A geometric mean of the normalized scores is then computed as the final score for the tile. Finally, the resulting per-tile scores are summed to create the application workload portion of the final metric.
A similar calculation is used to create the infrastructure workload portion of the final metric except that, unlike the application workloads, the infrastructure workloads are not scaled explicitly by the user. Consequently, the infrastructure workloads are compiled as a single group and no multi-tile sums are required.
The final benchmark score is computed as a weighted average: 80% to the application workload component and 20% to the infrastructure workload component. These weights were chosen to reflect the relative contribution of infrastructure and application workloads to overall resource demands.
In order for the resultant benchmark score to be considered compliant, the benchmark run must also meet a number of conditions, including minimum quality-of-service requirements.
In addition to the overall benchmark score, a VMmark full disclosure report also includes the raw and normalized results for each underlying workload and complete details of the virtualization platform configuration. In some cases, studying the workload metrics along with the platform configuration can provide insight into system performance and scaling.
Power and cooling expenses are a substantial — and increasing — part of the cost of running a data center. Additionally, environmental considerations are a growing factor in data center design and selection. To address these issues, VMmark enables optional power measurement in addition to performance measurements. VMmark 3 benchmark results can be any of three types:
- Performance only (no power measurement)
- Performance with server power
- Performance with server and storage power
VMmark results with power measurement allow hardware purchasers to see not just absolute performance, but also absolute power consumption and performance per kilowatt. This makes it possible to consider both capital expenses and operating expenses in the selection of new datacenter components.
VMmark 3 can automatically collect ESXTOP power data from the servers hosting VMmark application workloads. When enabled, this provides power usage tracking based on the server's power supply sensor.
Note: Though VMmark uses the SPEC® PTDaemon, VMmark results are not SPEC metrics and cannot in any manner be compared to SPEC metrics. ESXTOP power data cannot be used in published results or compared to PTDaemon metrics.
Besides the need to capture key performance characteristics of virtual systems, an appropriate virtual platform benchmark must employ realistic, diverse workloads running on multiple hosts. Further, there is a need to define a single, easy to understand metric while ensuring that the benchmark is representative of various end-user environments. The benchmark specification must provide a methodical way to measure scalability so that the same benchmark can be used for small platforms as well as larger platforms from different hardware vendors.
VMware realized the need for a next-generation virtualization benchmark to compare different virtualization and hardware platforms, which consists of multiple hosts, diverse multi-tier workloads and infrastructure operations. VMmark 3 was created as a standardized way to compare these platforms.
A VMmark tile is group of nineteen virtual machines concurrently executing a collection of diverse workloads. Each of these workloads represents a common multi-tier application workload found in today's data centers. Included in each tile are a scalable web simulation, an e-commerce simulation, and an idle machine.
Each virtual machine in a tile is tuned to use only a fraction of the system's total resources. As a tile, the aggregate of all workloads utilizes less than the full capacity of modern servers. The saturation of a system's resources and accurate measurement of server performance with VMmark 3 therefore requires the simultaneous execution of multiple tiles.
Each workload within a VMmark 3 tile is constrained to execute at less than full utilization of its virtual machine. The performance of each workload can vary to a degree with the speed and capabilities of the underlying system. For example, disk-centric workloads might respond to the addition of a fast disk array with a more favorable score. These variations can capture system improvements that don't warrant the addition of another tile. The workload throttling will force the use of additional tiles for large jumps in system performance. When the number of tiles is increased, workloads in existing tiles might have lower performance. If the system has not been overcommitted, the aggregate score, including the new tile, should increase. The result is a flexible benchmark metric that provides a relative measure of the number of workloads that can be supported by a particular system as well as the cumulative performance level of all the virtual machines.
VMmark 3 was developed as a tool for hardware vendors, system integrators, and customers to evaluate the performance of their systems. Many customers will not run the benchmark themselves, but rather rely on published VMmark 3 scores from their hardware vendors to make purchasing and configuration decisions for their virtualization infrastructure.
The main use-case for VMmark 3 is to compare the performance of different hardware platforms and configurations. Organizations implementing or evaluating virtualization platforms use VMmark 3 for comparing performance and scalability of different virtualization configurations, making appropriate hardware choices, and for measuring platform performance on an ongoing basis.
It is also important to note that VMmark 3 is neither a capacity planning tool nor a sizing tool. It does not provide deployment guidelines for specific applications. Rather VMmark 3 is meant to be representative of a general-purpose virtualization environment. The virtual machine configurations and the software stacks inside the virtual machines are fixed as part of the benchmark specification. Recommendations derived from VMmark 3 results will capture many common cases; however, specialized scenarios will likely require individual measurement.
With VMmark 3, organizations have a robust and reliable benchmark that captures the key performance characteristics of virtual platforms, is representative of real world environments running multiple workloads, is hardware platform neutral, and provides a methodical way to measure scalability so that the same benchmark can be used across different vendor platforms.
A higher VMmark 3 score implies that a virtualization platform is capable of sustaining greater throughput in a mixed workload cloud environment, while experiencing data center operations in the background. A larger number of VMmark 3 tiles used to generate the benchmark means that the platform supported more virtual machines across the multiple hosts during the benchmark run. Typically a higher benchmark score requires a higher number of tiles.
If two different virtualization platforms achieve similar VMmark 3 scores with a different number of tiles, the score with the lower tile count is generally preferred. The higher tile count could be an indication that the underlying hardware resources were not properly balanced. Studying the individual workload metrics is suggested in these cases.
The workload applications in VMmark 3 have been updated to reflect modern multi-tier application design standards and technologies. VMmark 3 features a highly automated setup and tile-cloning process, and the VMmark .ova includes all the needed software in one downloadable template.
No, the workloads and load levels of VMmark 3 have changed significantly from VMmark 2.x in order to take better advantage of today's larger and more powerful server hardware. Because the VMmark 3 workloads and load levels have changed since VMmark 2.x, the VMmark 3 benchmark scores are not comparable to VMmark 2.x benchmark scores.
No. VMmark 3 provides three test types:
Benchmarkers may choose to optimize a test configuration for a particular aspect of measurement. For instance, if running with a power measurement, the benchmarker may choose to optimize for power over server performance. Representing all server performance results (both with and without power measurements) on the same results page could be misleading. In order to ensure consistent comparability of results, separate results pages are used.
To qualify as a vSAN storage result, a VMmark result must run all application workload virtual machines on VMware vSAN storage. However, these results can use non-vSAN storage hardware for infrastructure target storage and for the deploy template. For more details, see section 3.2.2 in the VMmark Run and Reporting Rules.
To view vSAN storage results, see Recently Published vSAN Storage on the VMmark Results Page.
There are a number of sources for VMmark support:
This section provides an abbreviated outline of the VMmark 3 system requirements. For a detailed list, see the most recent version of the VMmark User’s Guide (on the VMmark download page, available after accepting the VMmark EULA).
VMmark 3.x Hardware Requirements
This section lists the minimum hardware required to run VMmark.
Note that this is the bare minimum. Most VMmark installations will use significantly more hardware than listed here.
A 2-host cluster (homogeneous systems not required), with the following:
VMware vCenter Server installed on a separate, dedicated server
One Prime Client virtual machine with:
One client virtual machine per tile, each with:
Virtual client hosts with the following:
vMotion networking (10 Gbps network recommended)
To get started with VMmark, follow these steps: