Since we are virtualizing many of our Linux servers, this post was of interest to us:
"VMmark 1.0 utilized only 32-bit workloads, which was a reasonable mix when the benchmark was first defined roughly three years ago. However, 64-bit applications and OSes are becoming much more prevalent and we need the ability to characterize this more complex reality. To address this, [for vmware 1.1] we have transitioned three of the VMmark workloads - Java server, database server, and web server - to 64-bit. In order to maintain comparability with the existing version 1.0 results, we have retained the underlying virtual hardware definitions and load levels for each workload."
This will let us benchmark our specific ESX host setup and test Oracle Linux VM servers under various settings...
"VMmark 1.0 utilized only 32-bit workloads, which was a reasonable mix when the benchmark was first defined roughly three years ago. However, 64-bit applications and OSes are becoming much more prevalent and we need the ability to characterize this more complex reality. To address this, [for vmware 1.1] we have transitioned three of the VMmark workloads - Java server, database server, and web server - to 64-bit. In order to maintain comparability with the existing version 1.0 results, we have retained the underlying virtual hardware definitions and load levels for each workload."
This will let us benchmark our specific ESX host setup and test Oracle Linux VM servers under various settings...
Comments