BizTalk 2009 Performance

SBPCT301 BizTalk 2009 Performance Ewan Fairweather Tim Wieman Paolo Salvatori BizTalk Customer Advisory Team (CAT) Microsoft Corporation

Session Objectives • Session Objective(s): • Provide illustrative examples of successful performance labs. • Provide information on the tools, techniques and processes used by the Rangers to run effective BizTalk performance labs. • Answer BizTalk performance related questions.

Results for Customer Performance Lab Initial results for BizTalk 2009 Performance Lab Visual Studio Test Demo Optimization Highlights & Open Q&A Agenda

Skandia Background • Existing ASP.NET COM+ based internet bank • New version of internet bank: • Go-live November 2008 • SOA based • BizTalk used as Skandia’s Service Bus • Leverages investments Skandia have made in IKForetag (Insurance application) • Current throughput 100,000 requests per day • Two-year projected growth to 250,000 requests per day • Will solidify BizTalk/WCF as the messaging platform for the bank • Ranger involvement • ADR delivered June 2008 • Performance Lab scheduled September 2008

Skandia Performance Lab Goals Determine if the BizTalk Server 2006 solution can meet the following performance requirements given hardware and software constraints: • Scenario 1 • Orchestration scenario • Throughput: 250,000 calls within 8 hours ~9 messages/sec sustainable • Latency: < 3 seconds for 99% of all response messages • Scenario 2 • Messaging scenario • Throughput: 250,000 calls within 8 hours ~9 messages/sec sustainable • Latency: < 3 seconds for 99% of all response messages • Conditions • No restriction on code changes • Additional hardware can be used if necessary • Start the solution testing with 2 BizTalk Server nodes and scale out to 4 BizTalk Server nodes • Considerable knowledge transfer

Skandia Scenarios Overview • Scenario 1: Orchestration • Scenario 2: Messaging only

Scenario 1 Message FlowOrchestration Scenario 4 3 2 5 1 6

~333% throughput improvement* ~195% of throughput requirements* Latency reduced to ~29% of original value* Stability validated by long running test *2 BizTalk Node Configuration Skandia Scenario 1 Results Summary 1 2 3 4 7 8 5 6

Scenario 2 Message FlowMessaging only 2 3 4 1

~480% throughput improvement* ~2000% of throughput requirements* Latency reduced to ~36% of original value* Stability validated by long running test *2 BizTalk Node Configuration Skandia Scenario 2 Results Summary 1 2 3 4 7 8 5 6

Logical Ports Test Scenario Logical Port Orchestration

Performance Comparison Summary Vs. Vs. 1 2 3

Inline Sends and Logical Ports Logical Port Orchestration Vs. Inline Sends Orchestration

Logical Ports and Inline Sends Results Summary Constant load 1 2 3 4 Stair step 7 8 5 6

Visual Studio Demo

Agenda Results for Customer Performance Lab Initial results for BizTalk 2009 Performance Lab Visual Studio Test Demo Optimization Highlights & Open Q&A

Platform Optimization Highlights • Adjusted Windows Server 2008 for best performance • Disabled SynAttackProtect (Denial of Service checking) • Placed the PAGEFILE on a separate local disk • Changed the Speed & Duplex property of each NIC from “Auto” to 1 Gigabit Full Duplex • Stopped and disabled unused windows services on all BizTalk Server and SQL Server nodes • Disabled the debug flag in the web.config configuration files • Increased the maxconnection settings from the default value of 2 to 50 on BizTalk and Front-End web farm The following settings did not improve performance on Windows Server 2008 which has a self tuning network stack: • Modified or created several registry entries regarding TCP/IP, Network, Session Manager, LanManServer, FileSystem settings.

SQL Optimization Highlights • Before baseline: • Installed CU package 9 and installed Performance Dashboard • Pre-allocate space (size) for all data / log files • Fixed autogrowth value to a fixed amount • Granted Windows ‘Lock Pages In Memory’ and ‘Perform Volume Maintenance Task’ • Standard SQL optimizations: • Moved Data and Log files to separate LUNs • Output all Log/Full backups to dedicated LUN • Split TempDB into multiple equal sized files • Relieving contention on MessageBox: • R2 BizTalk stored procedures - Hotfix KB944234 • Spread tables and indexes of the BizTalkMsgBoxDb across multiple filegroups / multiple LUNs • Changed schedule of BizTalk ‘Mark Log’ backup job from 15 to 5 minutes • Scaling out: • Created dedicated SQL Server instance for BizTalkMsgBoxDb • Moved BizTalkMsgBoxDb to a dedicated Server

BizTalk Optimization Highlights • R2 64 bit BizTalk hosts take ~1 minute to restart • Installed KB943165 • Separated hosts (including dedicated tracking host) • BizTalk HTTP connections increased from 2 to 50 • Disabled Message Delivery throttling • Disabled global tracking as in the production site. • Reduced the MaxReceiveInterval to 50 ms (default 500 ms) in the adm_ServiceClass table • Increased the Internal Message Queue Size from the default value 100 to 1000 for all the BizTalk Hosts • Disabled orchestration tracking events • Disabled BAM • Increased the .NET CLR worker and IO threads for all the in-process hosts • Optimized WCF Adapter settings

Reduce costs and expenses Win market share from expensive competitors Optimize to do more with less! Delight our customers. Why Tune BizTalk Now - More than Ever?

© 2009 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

BizTalk 2009 Performance