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 Incoming Rate Received/Sec BizTalk Messaging TxHost Documents Outgoing Rate Processed/Sec XLANG/s Orchestrations PxHost Orchestrations Processing Rate Completed/Sec. BizTalk : MessageBox: MsgBoxName Spool Size Cumulative size General Counters of all Host Queues BizTalk : MessageBox: MsgBoxName Tracking Data Size Size of General Counters TrackingData table on the MessageBox BizTalk:MessageBox:Host PxHost:MsgBoxName Host Queue - Number of Counters Length messages in the
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
BizTalkServer2013-PerformanceGuide.docx