Performance/vConsolidate-SMP - Revision history

Kir: Reverted edits by 18.85.56.20 (talk) to last revision by Vlukovnikov

2011-11-28T05:23:36Z

Reverted edits by 18.85.56.20 (talk) to last revision by Vlukovnikov

18.85.56.20: /* TODO */

2011-11-28T04:52:26Z

‎TODO

Vlukovnikov: OpenVZ RH5 version - upgrade to 2.6.18-028stab090.4

2011-05-16T10:18:42Z

OpenVZ RH5 version - upgrade to 2.6.18-028stab090.4

Vlukovnikov at 12:23, 13 May 2011

2011-05-13T12:23:31Z

Dev at 09:13, 22 April 2011

2011-04-22T09:13:00Z

Vlukovnikov at 18:23, 15 April 2011

2011-04-15T18:23:46Z

Vlukovnikov: Created page with '=== Benchmark Description === This benchmark is designed to measure aggregated server performance in consolidation scenario: where different apps are running at the same time in…'

2011-04-15T18:20:45Z

Created page with '=== Benchmark Description === This benchmark is designed to measure aggregated server performance in consolidation scenario: where different apps are running at the same time in…'

New page

=== Benchmark Description ===

This benchmark is designed to measure aggregated server performance in consolidation scenario: where different apps are running at the same time in separate virtual machines or operating system containers.

=== Implementation ===

We use standard industrial benchmark: vConsolidate. It was developed by Intel in cooperation with other vendors. vConsolidate measures performance from Java, Web and Db VMs running concurrently (we excluded Mail VM as it was MS Windows version only). Each set of such three VMs is called CSU - Consolidation Stack Unit.
Performance metric is geomean from throughput of each workload type: transactions/sec for Db, requests/sec for Web and java operations/sec for Java.

=== Testbed Configuration ===
Server: 4xHexCore Intel Xeon (2.66 GHz), 64 GB RAM, HP MSA1500 SAN Storage, 8 SATA (7200 RPM) Disks in RAID0

Client: 4xHexCore Intel Xeon (2.136 GHz), 32 GB RAM

Network: Gbit direct server<>client connection

Virtualization Software: XenServer5.6fp1, OpenVZ (RH5) 2.6.18-028stab085.3, OpenVZ (RH6) 2.6.32-042test006.1.x86_64

Guest OS: Centos 5.5 x86_64

Software and Tunings:
* Firewall was turned off
* All other tunings were left at default values

=== Benchmark Results ===

[[File:vConsolidate-SMP.png]]

=== Summary ===

*TODO: write summary

← Older revision		Revision as of 05:23, 28 November 2011
Line 37:		Line 37:
	* 2.1-2.2x times better overall performance on 5 and 10 CSU.		* 2.1-2.2x times better overall performance on 5 and 10 CSU.

−	~~If time is money you've made me~~ a ~~weatliher woman~~.	+	=== TODO ===
		+	* add a link to paper where explaining why containers are great for SMP workloads and CPU overcommit.

← Older revision		Revision as of 04:52, 28 November 2011
Line 37:		Line 37:
	* 2.1-2.2x times better overall performance on 5 and 10 CSU.		* 2.1-2.2x times better overall performance on 5 and 10 CSU.

−	~~=== TODO ===~~	+	If time is money you've made me a weatliher woman.
−	* add a ~~link to paper where explaining why containers are great for SMP workloads and CPU overcommit~~.

@@ Line 18: / Line 18: @@
 Platform:
-* Virtualization Software: ESXi4.1up1, XenServer5.6fp1, OpenVZ (RH5) 2.6.18-028stab085.3, OpenVZ (RH6) 2.6.32-042test006.1.x86_64
+* Virtualization Software: ESXi4.1up1, XenServer5.6fp1, OpenVZ (RH5) 2.6.18-028stab090.4, OpenVZ (RH6) 2.6.32-042test006.1.x86_64
 * Guest OS: Centos 5.5 x86_64

@@ Line 18: / Line 18: @@
 Platform:
-* Virtualization Software: XenServer5.6fp1, OpenVZ (RH5) 2.6.18-028stab085.3, OpenVZ (RH6) 2.6.32-042test006.1.x86_64
+* Virtualization Software: ESXi4.1up1, XenServer5.6fp1, OpenVZ (RH5) 2.6.18-028stab085.3, OpenVZ (RH6) 2.6.32-042test006.1.x86_64
 * Guest OS: Centos 5.5 x86_64
@@ Line 38: / Line 38: @@
 === TODO ===
 * add a link to paper where explaining why containers are great for SMP workloads and CPU overcommit.

@@ Line 1: / Line 1: @@
 === Benchmark Description ===
-This benchmark is designed to measure aggregated server performance in consolidation scenario: where different apps are running at the same time in separate virtual machines or operating system containers.
+The goal of Intel vConsolidate benchmark is to measure aggregated server performance in consolidation scenario: when different (and non-related unlike to LAMP benchmark) applications are running on the same box each in its own virtual environment (virtual machine or container).
 === Implementation ===
-We use standard industrial benchmark: vConsolidate. It was developed by Intel in cooperation with other vendors. vConsolidate measures performance from Java, Web and Db VMs running concurrently (we excluded Mail VM as it was MS Windows version only). Each set of such three VMs is called CSU - Consolidation Stack Unit.
+Intel vConsolidate v1.1. We do not run Mail VM as Intel benchmark has Microsoft Windows version only for mail workload.
 === Testbed Configuration ===
-Server: 4xHexCore Intel Xeon (2.66 GHz), 64 GB RAM, HP MSA1500 SAN Storage, 8 SATA (7200 RPM) Disks in RAID0
+Hardware:
-Client: 4xHexCore Intel Xeon (2.136 GHz), 32 GB RAM
+Platform:
+* Virtualization Software: XenServer5.6fp1, OpenVZ (RH5) 2.6.18-028stab085.3, OpenVZ (RH6) 2.6.32-042test006.1.x86_64
-Network: Gbit direct server<>client connection
+* Guest OS: Centos 5.5 x86_64
 Software and Tunings:
@@ Line 24: / Line 25: @@
 * Custom vConsolidate profile was used: 4 load threads for Java workload, 4 load threads for Db workload and 8 threads for Web workload (standard setting)
 * Firewall was turned off
-* All other tunings were left at default values
+* All other settings were left as defaults
 === Benchmark Results ===
@@ Line 32: / Line 33: @@
 === Summary ===
-*TODO: write summary
+OpenVZ demonstrates outstanding performance benefits over hypervisors in case of multi-processor environments and multi-threaded workloads: