Here are some things to consider related to operating system performance:
- Distributed transactions can add overhead. Before a transaction is completed, an acknowledgment (ACK) must be received from the remote server. Delays with the remote server or with the network between the servers should be investigated.
- When Kerberos is used, the Privilege Attribute Certificate (PAC) verification process may increase network traffic. PAC verification can be disabled as documented in KB article 906736: You experience a delay in the user-authentication process when you run a high-volume server program on a domain member in Windows 2000 or Windows Server 2003.
- There are several TCP settings that directly affect performance, including the Scalable Networking Pack (SNP) features, SynAttackProtect and MaxUserPort. KB article 970406: TCP settings that can impact BizTalk Server provides more information about these settings.
- Anti-virus software is typically configured to scan/monitor folders on the server. The BizTalk folders should be excluded in any AV scanning software.
- If the MSMQ adapter is being used, there could be issues if the MSMQ storage folder is near capacity. MSMQ Message Storage is discussed in Message Storage.
- If the File adapter is being used, the MaxCmds value might be exceeded, and could result in an "exhausted the network retry attempts" error. For more information, see KB article 952556: File receive locations are disabled or shut down on a computer that is running BizTalk Server and KB article 810886: "The network BIOS command limit has been reached" error message in Windows Server 2003, in Windows XP, and in Windows 2000 Server.
- If a BizTalk service fails to start after restarting, it's possible that a third-party/custom service could be causing this. On Windows Server 2008, you can try setting the BizTalk service for Automatic (Delayed Start).
- Mismatched duplex settings between computers running BizTalk Server and SQL Server have caused performance issues. The network interface card (NIC) card drivers should also be current.
- CLR Hosting registry settings affect the .NET thread pool, which BizTalk Server uses. If thread starvation occurs, the CLR Hosting registry keys documented in Configuration Parameters that Affect Adapter Performance can be modified.
- Any disk issues, especially on the remote computer running SQL Server, should be resolved. This sometimes requires the hardware vendor to analyze the situation. You can use Performance Monitor to determine if there are disk issues.
- Low-paged pool and non-paged pool memory should be avoided. PoolMon and MPS Reports can be used to determine what is using the most paged pool and non-paged pool memory. KB article 298102: How to find pool tags that are used by third-party drivers may also be helpful.
- General performance problems including high memory usage and/or high CPU should be resolved. If high memory is normal, consider using a 64-bit server. If high CPU is also normal, consider new/additional hardware.
To troubleshoot:
- If you suspect delays with Distributed Transactions, you can capture a Distributed Transaction Coordinator (DTC) trace to see how long a transaction took from creation to completion. KB article 899115: How to enable diagnostic tracing for MSDTC on a computer that is running Windows XP or Windows Server 2003 provides more information about DTC tracing. You can also collect memory dumps in hang mode of the client process, server process, and MSDTC. For analysis, you can contact Microsoft Customer Service and Support (CSS).
- If you suspect a third-party/custom service could be causing problems, you can use the Services tab in msconfig to disable a handful of third-party services. Restart, and see if the issue persists. You may have to do this several times.
- If you suspect a delay in the network, use Network Monitor to obtain simultaneous network captures between the servers. KB article 933741: Information about Network Monitor 3 provides more information about Network Monitor 3.0.
- The Physical Disk, Logical Disk and Processor Performance Monitor objects can be used to determine if there is a disk issue. The bottleneck-detection counters are described in Bottleneck-Detection Counters.
- Capturing memory dumps of a high memory or high CPU process can be used to determine root cause. For debug analysis, you can contact Microsoft Customer Service and Support (CSS).
|
|