Editing Performance/LAMP

Jump to: navigation, search

Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision Your text
Line 1: Line 1:
 
=== Benchmark Description ===
 
=== Benchmark Description ===
 
+
LAMP (acronym for Linux, Apache, MySQL, PHP) software stack is widely used for building modern web sites. We measure not only performance (how many requests can deliver server), but also maximum response time - to understand QoS.
LAMP (acronym for Linux, Apache, MySQL, PHP) software stack is widely used for building modern web sites on Linux. So it's quite natural that there is a need to understand how well such type of workloads run in virtualized environment and how many LAMPs virtualization can bare on a single piece of hardware. 2 important metrics are presented in this report: total number of serviced requests/sec and average response time.
 
  
 
=== Implementation ===
 
=== Implementation ===
  
To measure LAMP software stack performance and density we use DVD-Store E-Commerce benchmark developed by [http://linux.dell.com/dvdstore/ Dell]. This benchmark is also widely used by RedHat and others.
+
To measure LAMP software stack performance and density we use DVD-Store E-Commerce benchmark developed by [http://linux.dell.com/dvdstore/ Dell].  
  
 
=== Testbed Configuration ===
 
=== Testbed Configuration ===
Hardware:
+
Server: 4xHexCore Intel Xeon (2.66 GHz), 64 GB RAM, HP MSA1500 SAN Storage, 8 SATA (7200 RPM) Disks in RAID0
* 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
+
Client: 4xHexCore Intel Xeon (2.136 GHz), 32 GB RAM
* Network: 1Gbit direct server <-> client connection
+
 
 +
Network: Gbit direct server<>client connection
 +
 
 +
Virtualization Software: ESXi4.1upd1, XenServer5.6fp1, HyperV (R2), OpenVZ (RH6) 2.6.32-042test006.1.x86_64
  
Platform:
+
Guest OS: Centos 5.5 x86_64
* Virtualization Software: ESXi4.1upd1, XenServer5.6fp1, HyperV (R2), OpenVZ (RH6) 2.6.32-042test006.1.x86_64
 
* Guest OS: Centos 5.5 x86_64
 
  
 
Software and Tunings:
 
Software and Tunings:
Line 34: Line 34:
 
=== Summary ===
 
=== Summary ===
  
* OpenVZ shows the best performance over solutions tested: OpenVZ 38% faster than XenServer and more than x2 times faster than HyperV and ESXi under high load.
+
* OpenVZ shows the best performance over solutions tested: OpenVZ 38% faster than XenServer and more than x2 times faster than HyperV and ESXi
* OpenVZ shows the best response time over solutions tested: 33% better response time compared to ESXi and x2 times better response time than XenServer and HyperV
+
* OpenVZ shows the best response time over solutions tested: OpenVZ has 33% better response time than ESXi and x2 times better response time than XenServer and HyperV

Please note that all contributions to OpenVZ Virtuozzo Containers Wiki may be edited, altered, or removed by other contributors. If you don't want your writing to be edited mercilessly, then don't submit it here.
If you are going to add external links to an article, read the External links policy first!

To edit this page, please answer the question that appears below (more info):

Cancel Editing help (opens in new window)