Test Machine Configurations

This topic provides detailed information about the machine and environment configurations for the test scenarios.

For each of the servers that were installed the following settings were adjusted.

For all servers:

  • The paging file was set to 1.5 times the amount of physical memory allocated. The paging file was set to a fixed size by ensuring that the initial size and maximum values were identical in MB

  • The “Adjust for best performance” performance option was selected from the advanced System Properties screen

  • It was verified that the system had been adjusted for best performance of Background services in the Performance Options section of System Properties

  • Windows 2003 R2 SP2 was installed as the guest operating system on each of the virtual machines

  • Windows Update was successfully run on all servers to install the latest security updates

For SQL Servers:

  • SQL Server 2005 SP2 was installed as per the installation guide available at http://go.microsoft.com/fwlink/?LinkId=105010.

  • Each SQL Server used had the SAN LUNs configured as per the table below. The database and log files were separated to across the LUNs as follows to reduce possible disk I/O contention:

    • The Data_Sys volume was used to store all database files (including system and BizTalk databases) except the MessageBox and TempDb databases

    • The Log_Sys volume was used to store all log files (including system and BizTalk databases) except the MessageBox and TempDb databases

    • The Data_TempDb volume was used to store the TempDb database file

    • The Logs_TempDb volume was used to store the TempDb log file

    • The MessageBox database file was stored on the Data_BtsMsgBox volume and the log file was stored on the Log_BtsMsgBox volume

  • In addition to this a separate LUN was provided for the MSDTC log file. On high throughput BizTalk systems the MSDTC log file activity has been shown to cause a I/O bottleneck if it is left on the same physical drive as the operating system.

Drive Volume Name LUN Size GB Host Partition Size GB RAID Configuration

G:\

Data_Sys

50

50

RAID 0 + 1

H:\

Logs_Sys

50

50

RAID 0 + 1

I:\

Data_TempDb

50

50

RAID 0 + 1

J:\

Logs_TempDb

50

50

RAID 0 + 1

K:\

Data_BtsMsgBox

300

50

RAID 0 + 1

L:\

Logs_BtsMsgBox

100

50

RAID 0 + 1

M:\

MSDTC

5

5

RAID 0 + 1

A single fixed VHD was used for to host the operating system for each Hyper-V virtual machine. 30GB of space was allocated to each VHD and it was partitioned within the guest operating system as follows:

  • C:\ Operating System, 12 GB partition

  • D:\ Program Files, 8 GB partition

  • E:\ Paging File, 10 GB partition

Fixed VHDs were used instead of dynamically sized VHDs because they immediately allocate the maximum storage for the VHD to the file on the drive where it is hosted. This reduces fragmentation of the VHD file occurring on the physical drive where it is hosted, which improves disk I/O performance.

Pass-through disks were configured for the SAN-attached storage for the virtual SQL Server machines that were used in test scenario 3. The LUN configuration for the SAN used identical configuration on both the physical and virtualized SQL Server environments. Pass-through disks were chosen for this to ensure optimal I/O performance for the BizTalk Server database files.

To set-up the virtual machines, an installation of Windows 2003 R2 64-bit edition was performed on a single VHD. Once Service Pack 2 and all appropriate updates had been installed the image was imaged using the 64-bit SP2 version of SysPrep which is available at http://go.microsoft.com/fwlink/?LinkId=122842.

This base VHD was then copied and used as the basis for all Hyper-V virtual machines that were deployed across the environment. Sysprep was run on the base VHD image to reset (or “reseal”) system security identifiers before any SQL Server or BizTalk binaries were deployed to the system.

Cc768533.note(en-US,BTS.10).gif
Running Sysprep after BizTalk has been installed and configured on the server is not supported, because Sysprep cannot adjust the server names, security identifiers, and other security-related information stored by BizTalk Server.

For additional background information and resources on Hyper-V, see the Getting Started section.

Summary of Test Scenarios provides a detailed summary of test results when comparing performance of a BizTalk Server solution running on a Windows Server 2003 guest operating system installed on Hyper-V virtual machine(s) and a BizTalk Server solution running on an operating system installed on physical hardware. The following section provides an overview of the architecture used for these tests and a summary of the test results.

Virtualization testing architecture summary – The graphic below is representative of the lab hardware used in the lab to test performance of a BizTalk Server solution running on a Windows Server 2003 guest operating system installed on Hyper-V virtual machine(s). Note that the number of physical and virtual machines in this configuration varied depending on the particular test scenario but this graphic provides a general configuration of the lab hardware that was used during testing:

Cc768533.79edc8f3-53d8-4e88-aa19-4cbcfd700e69(en-US,BTS.10).gif

The table below provides a summary of the physical hardware used in the lab:

Computer roleComputer nameCPU type# of CPUsCores per processorCPU architectureMemory installedOperating system

Monitoring computer

Monitoring_M01

AMD Opteron 2.2ghz

2

2

x86

2GB

Windows Server 2003 SP2 Enterprise 32-bit

Visual Studio and load generator

VS_Loadgen_L01

AMD Opteron 2.2ghz

2

2

x86

2GB

Windows Server 2003 SP2 Enterprise 32-bit

Load generator

Loadgen_L02

AMD Opteron 2.2ghz

2

2

x86

2GB

Windows Server 2003 SP2 Enterprise 32-bit

Load generator

Loadgen_L03

AMD Opteron 2.2ghz

2

2

x86

2GB

Windows Server 2003 SP2 Enterprise 32-bit

Load generator

Loadgen_L04

AMD Opteron 2.2ghz

2

2

x86

2GB

Windows Server 2003 SP2 Enterprise 32-bit

Load generator

Loadgen_L05

AMD Opteron 2.2ghz

2

2

x86

2GB

Windows Server 2003 SP2 Enterprise 32-bit

Web services

WebSvc_WS01

Intel Xeon 3 Ghz

4

1 (HyperThreading enabled)

x86

4GB

Windows Server 2003 SP2 Enterprise 32-bit

Physical SQL Server

Physical_SQL01

Intel Xeon 2.33Ghz

2

4

x64

4GB

Windows Server 2003 R2 SP2 Enterprise 64-bit

Physical BizTalk Server

Physical_BTS01

Intel Xeon 2.33Ghz

2

4

x64

4GB

Windows Server 2003 R2 SP2 Enterprise 64-bit

Hyper-V physical computer

Hyper-V_01

Intel Xeon 2.33Ghz

2

4

x64

8GB

Windows Server 2008 Enterprise 64-bit

Hyper-V physical computer

Hyper-V_02

Intel Xeon 2.33Ghz

2

4

x64

4GB

Windows Server 2008 Enterprise 64-bit

Hyper-V physical computer

Hyper-V_03

Intel Xeon 2.4Ghz

4

4

x64

32GB

Windows Server 2008 Enterprise 64-bit

Virtual SQL Server

Virtual_SQL01

Intel Xeon 2.33Ghz

2

4

x64

2GB

Windows Server 2003 R2 SP2 Enterprise 64-bit

Virtual SQL Server

Virtual_SQL02

Intel Xeon 2.33Ghz

2

4

x64

4GB

Windows Server 2008 Enterprise 64-bit

Virtual SQL Server

Virtual_SQL03

Intel Xeon 2.33Ghz

2

4

x64

2GB

Windows Server 2003 R2 SP2 Enterprise 64-bit

Virtual BizTalk Server

Virtual_BTS01

Intel Xeon 2.33Ghz

2

4

x64

Memory allocated to Hyper-V virtual machines running BizTalk Server varied depending on the test scenario, ranging between a minimum of 1.5 GB to a maximum of 2GB

Windows Server 2003 R2 SP2 Enterprise 64-bit

Virtual BizTalk Server

Virtual_BTS02

Intel Xeon 2.33Ghz

2

4

x64

4GB

Windows Server 2003 R2 SP2 Enterprise 64-bit

Virtual BizTalk Server

Virtual_BTS03

Intel Xeon 2.33Ghz

2

4

x64

4GB

Windows Server 2003 R2 SP2 Enterprise 64-bit

Virtual BizTalk Server

Virtual_BTS04

Intel Xeon 2.33Ghz

2

4

x64

4GB

Windows Server 2003 R2 SP2 Enterprise 64-bit

Virtual BizTalk Server

Virtual_BTS05

Intel Xeon 2.33Ghz

2

4

x64

4GB

Windows Server 2003 R2 SP2 Enterprise 64-bit

Virtual BizTalk Server

Virtual_BTS06

Intel Xeon 2.33Ghz

2

4

x64

4GB

Windows Server 2003 R2 SP2 Enterprise 64-bit

Virtual BizTalk Server

Virtual_BTS07

Intel Xeon 2.33Ghz

2

4

x64

4GB

Windows Server 2003 R2 SP2 Enterprise 64-bit

Virtual BizTalk Server

Virtual_BTS08

Intel Xeon 2.33Ghz

2

4

x64

4GB

Windows Server 2003 R2 SP2 Enterprise 64-bit

Show: