Search code examples
performancesoapbiztalkasmx

BizTalk SOAP receive location poor performance


I've encountered poor performance in my BizTalk application that uses SOAP/ASMX Receive location web service hosted in IIS on the same sever. This service only invoke one function on Oracle DB (connected via Oracle Driver)

I've done load tests via Soap UI and I stressed DB a little from PL/SQL Profiler in SQL Navigator and it turned out that avg request time = 700ms, avg DB query time = 15ms, avg Orchestration done time = 30ms (via BT Admin Console), so there is an tremendous amount of time wasting by IIS, asmx or SOAP?

I've read this: Configuration Parameters that Affect Adapter Performance and tweaked minFreeThreads , minFreeLocalRequestFreeThreads but nothing really happened.

But as I understand well - there is send port described there and I have problem Receive Location, right?

Also read that article: BizTalk: Performance problems using the SOAP adapter

There is no such key like:

Registry Key:

HKLM\SYSTEM\CurrentControlSet\Services\BTSSvc$BizTalkServerApplication\CLR Hosting

How to achieve Option 2?

Option 2:

Look into process isolation – this would using a different instance of the .NET threadpool executed in a separate address space from the BizTalk NT service.

Guide me please


Solution

  • Go to your receive host properties and change message polling interval to 50ms from default 500ms, that will provide an improved performance. If you're using orchestration on a separate host to process service request and response, do the same on orchestration host but reduce orchestration polling interval. Doing this increase performance for low latency scenario, however it adds overhead on SQL message box. Depending on your volume and need tune this.

    Also try upgrading to WCF services