As promised I have some results from the tests.
So we compared HP ML 370 with 14 SAS disks dedicated to a HP DL380 with data on a HP MSA2000 SAS SAN running on VMWare with the same amounts of disks.
The DL380 is running on VMWare. The OS is on a shared storrage with the OS of the other VMWare machines.
We did the tests using the benchmark toolkit and some manual processes. The measuring was done using the SQL Perform Tools.
Besides comparing VMWare and SAN/DAS we compared 5.0 SP1 to RTM.
The results of the VMWare / DAS comparison are amazing. They are almost the same.
Heavy testing shows that VMWare is just slightly slower in posting but only 5% maximum.
Results of manual reading
1. 5.0 RTM on VMWare/SAN2. 5.0 SP1 on VMWare/SAN3. 5.0 RTM on Windows/DAS4. 5.0 SP1 on Windows/DAS
Manual reading means opening stuff like G/L and running some reports
Differences are minimal (5 - 10%)
Results of benchmark posting
1. 5.0 SP1 on Windows/DAS2. 5.0 RTM on Windows/SAN
3. 5.0 SP1 on VMWare/SAN4. 5.0 RTM on VMWare/SAN
A big remark here is that on SP1 we actualy needed some index hints! We got deadlocks we did not have on 5.0 RTM. I will blog about that later.
The customer is live now. This week we will continue to measure.
It is amazing to see VMWare running and the management and failover capabilities. For me it means the end of active passive clusters.
So is there still value of logshipping/log backups? Definately yes! At this customer we will put an old server in a separate room, far away from the server room. This will be the log shipping server.
If anything goes terribly wrong in the serverroom there will be a server with a max. 5 minutes old database.
Remember that even if everything is redundant the server can catch fire or water damage. This happens; really,
One of the things the customer has to do is place an extra airconditioning unit. The double MSA2000 is producing so much heat that the temperature raised 5 degrees! Plus the airconditioning is redunant to.
From one of my other customers (Katoen Natie) I got some tips.
- Use ESX version 3.5 Update 1. ESX 3.0.2 gives blue screens gehad on SQL 2005 x64 machines.
- Place disks on VMFS volumes.
- Install Windows 2003 SP2 + patches.
- Give all machines 1 vCPU or 2 vCPU’s, but no 4.
- Install machines from scratch and use the correct HAL gebruikt (Computer Management – Device Manager – Computer). for a 1 vCPU this must be the Uniprocessor HAL zijn. The Multiprocessor HAL works to but gives worse performance. With +2 vCPU’s thus must be Multiprocessor HAL.
FYI: KTN has over 100 Navision databases and is a SQL Perform user. We are very proud of that.
We verified all KTN's suggestions with our VMWare expert and found out that this is their default setup. :) They are great expers. More information on www.dewal-ict.nl
SQL Perform Benelux B.V.