Throttling impact Throttling will eventually start to protect the system from reaching an unrecoverable state. Thus, you can use throttling to verify whether the system is functioning normally and discover the source of the problem. After you identify the cause of the bottleneck from the throttling state, analyze the other performance counters to determine the source of the problem. For example, high contention on the MessageBox database could be due to high CPU use, caused by excessively paging to disk that is caused by low memory conditions. High contention on the MessageBox database could also be caused by high lock contention due to saturated disk drives. While occasional throttling is not a significant threat to performance, persistent throttling can indicate a more significant underlying problem. For more information about those conditions where BizTalk Server will use throttling, see (http://msdn.microsoft.com/library/aa559893(v=bts.80).aspx). For more information how BizTalk Server throttling can help manage the use of available resources and minimize resource contention, see (http://msdn.microsoft.com/library/aa561101(v=bts.80).aspx). BizTalk application counters The following tables are a sample consideration of Host Implementation and which performance counters to monitor: Object Instance Counter Description BizTalk Messaging RxHost Documents Received/Sec Incoming Rate BizTalk Messaging TxHost Documents Processed/Sec Outgoing Rate XLANG/s Orchestrations PxHost Orchestrations Completed/Sec. Processing Rate BizTalk : MessageBox: General Counters MsgBoxName Spool Size Cumulative size of all Host Queues BizTalk : MessageBox: General Counters MsgBoxName Tracking Data Size Size of TrackingData table on the MessageBox BizTalk:MessageBox:Host Counters PxHost:MsgBoxName Host Queue - Length Number of messages in the
The different performance states are dynamically managed by Windows in conjunction with hardware and platform firmware to respond to varying workload requirements. . The 3 default plans exposed by Windows provide varying tradeoffs of performance vs. power consumption. For example, if the High Performance power plan is selected, Windows places the system in the highest performance state and disables the dynamic scaling of performance in response to varying workload levels. Therefore, special care should be taken before setting the power plan to High Performance as this can increase power consumption unnecessarily when the system is underutilized. In some cases you may experience degraded overall performance on a machine when running with the default (Balanced) power plan. The issue may occur irrespective of platform and may be exhibited on both native and virtual environments. The degraded performance may increase the average response time for some tasks and cause performance issues with applications To change a power plan: Click on Start and then Control Panel. From the list of displayed item under Control Panel click on Power Options, which takes you to Select a power plan page. If you do not see Power Options, type the word 'power' in the Search Control Panel box and then select Choose a power plan. By default, the option to change power plans is disabled. To enable this, click the Change settings that are currently unavailable link. Choose the High Performance option Close the Power Option window. Disable non-essential services A default installation of Windows Server enables several services that may not be required in a BizTalk Server environment. Each running service consumes system resources and so unnecessary services should be disabled to improve overall performance. Care should be when disabling services. Thoroughly research the purpose of a service before disabling the service as Windows Server requires certain services are running. If services required by Windows Server are disabled, the operating system may become inoperable and possibly even unable to boot. To disable Windows Server services that are not required for a dedicated BizTalk Server, follow these steps: 1. Open Services (also available in Administrative Tools). 2. In the Status column, each service that is running is labeled "Started." Stop and disable any service that is started unnecessarily. For example, the following services are not required on a dedicated BizTalk Server:  Alerter  DHCP Server  Fax Service
value: Value closest to 64420 that is a multiple of the MSS value. exists by default? No, needs to be added. The EnableDynamicBacklog value is a global switch that enables AFD.SYS functionality to withstand large numbers of SYN_RCVD connections efficiently. EnableDynamicBacklog Key: EnableDynamicBacklog Data Type: REG_DWORD Range: 0 to 1 Default value: 0 value: 1 Value exists by default? No, needs to be added. The MinimumDynamicBacklog value spcifies the minimum number of free connections allowed on a listening endpoint. If the number of free connections drops below this value, a thread is queued to create additional free connections. MinimumDynamicBacklog Key: Value: MinimumDynamicBacklog Data Type: REG_DWORD Range: 0 to 4294967295 Default value: This value does not exist by default
Dell R710 2 x 3.3 GHz 6 x64 72 GB Windows Server 2012 Edition BizTalk Server 2013 Dell R710 Intel 2 x 3.3 GHz 6 x64 72 GB Windows Server 2012 Edition BizTalk Server 2013 Dell R710 Intel 2 x 3.3 GHz 6 x64 72 GB Windows Server 2012 Edition BizTalk Server 2013 SQL01 HP 4 x 2.3 GHz 4 x64 64 GB Windows Server 2012 Edition SQL Server 2012 HP DL585 Intel 4 x 2.3 GHz 4 x64 64 GB Windows Server 2012 Edition SQL Server 2012 SQL03 HP Intel 4 x 2.3 GHz 4 x64 64 GB Windows Server 2012 Edition SQL Server 2012 HP DL585 Intel 4 x 2.3 GHz 4 x64 64 GB Windows Server 2012 Edition SQL Server 2012 BTDC01 HP DL385 2 x 2.2 GHz 2 x64 8 GB Windows Server 2012 Edition Domain BTDC02 HP DL385 2 x 2.2 GHz 2 x64 8 GB Windows Server 2012 Edition Domain
Documents Processed per Second) SQL Processor Utilization) Documents Processed per Second) Processor Utilization) Single MessageBox 1 BizTalk Server computer 1407 documents processed per second 47.2% SQL CPU utilization 730 documents processed per second 69.3% SQL CPU utilization Single MessageBox 2 BizTalk Server computers 1471 documents processed per second 52.4% SQL CPU utilization 654 documents processed per second 65.7% SQL CPU utilization 1 MessageBox 3 BizTalk 1471 documents processed per second 52.4% SQL CPU utilization 660 documents processed per second 66.1% SQL CPU utilization 3 MessageBox 2 BizTalk Server computers 3060 documents processed per second 36% SQL CPU utilization 1088 documents processed per second 31.5% SQL CPU utilization 3 MessageBoxes 3 BizTalk Server computers 3060 documents processed per second 36% SQL CPU utilization 1216 documents processed per second 41% SQL CPU utilization Comparison of performance statistics with BizTalk Server 2009/2010 The following table shows a comparison of performance statistics between BizTalk Server 2009, 2010 and BizTalk Server 2013. The BizTalk Server 2013 performance statistics listed in this table are from the BizTalk Server 2010 Performance and Optimization Guide. (1 BTS, 1 MsgBox) BizTalk Server 2013 BizTalk Server 2010 BizTalk Server 2009 Messaging Only + No Tracking 1407 1266 1291* Orchestration(XMLDocument Rcv & Send) + No Tracking 730 680 676*(2 BizTalk Servers)