A Principled Technologies test report 15
Performance and TCO: Dell PowerEdge R820 vs.
HP ProLiant DL585 G7
After making these changes, we recompiled the ds2xdriver.cs and ds2sqlserverfns.cs module in Windows by
following the instructions in the DVD Store documentation. Because the DS2 instructions were for compiling from the
command line, we used the following steps on a system with Visual Studio installed:
1. Open a command prompt.
2. Use the cd command to change to the directory containing our sources.
3. Execute the following command:
csc /out:ds2sqlserverdriver.exe ds2xdriver.cs ds2sqlserverfns.cs
/d:USE_WIN32_TIMER /d:GEN_PERF_CTRS
Running the DVD Store tests
We created a series of batch files, SQL scripts, and shell scripts to automate the complete test cycle. DVD Store
outputs an orders-per-minute metric, which is a running average calculated through the test. In this report, we report
the last OPM reported by each client/target pair.
Each complete test cycle consisted of the general steps listed below. For each scenario, we ran three test cycles,
and chose the median outcome.
1. Clean up prior outputs from the host system and all client driver systems.
2. Drop all databases from all target VMs.
3. Restore all databases on all target VMs.
4. Shut down all VMs.
5. Reboot the host system and all client systems.
6. Wait for a ping response from the server under test (the hypervisor system), all client systems, and all VMs.
7. Let the test server idle for one hour.
8. Start the DVD Store driver on all respective clients.
We used the following DVD Store parameters for testing the virtual machines in this study:
ds2sqlserverdriver.exe --target=<target_IP> --ramp_rate=10 --run_time=30 --
n_threads=32 --db_size=5GB --think_time=0 --detailed_view=Y --warmup_time=5
Measuring power usage
To record each server’s power consumption during each test, we used an Extech® Instruments
(www.extech.com) 380803 Power Analyzer/Datalogger. We connected the power cord from the server under test to the
Power Analyzer’s output load power outlet. We then plugged the power cord from the Power Analyzer’s input voltage
connection into a power outlet.
We used the Power Analyzer’s Data Acquisition Software (version 2.11) to capture all recordings. We installed
the software on a separate Intel processor-based PC, which we connected to the Power Analyzer via an RS-232 cable.
We captured power consumption at one-second intervals.
To gauge the idle power usage, we recorded the power usage for two minutes while each system was running
the hypervisor and all 16 VMs, but otherwise idle, meaning they were not running any test workload.
We then recorded the power usage (in watts) for each system during the testing at one-second intervals. To
compute the average power usage, we averaged the power usage during the time the system was producing its peak
performance results. We call this time the power measurement interval.
(6 pages)
(16 pages)
Manymanuals.com
Manymanuals.de
Manymanuals.fr
Manymanuals.it
Manymanuals.pl
Manymanuals.cz
Manymanuals.es
Manymanuals-pt.com
Commentaires sur ces manuels